Self-Declaration of Fixed Assets by Custodians — A Practical Guide
Published: April 14, 2026
Every year, the finance department sends a team to verify fixed assets. The team walks through buildings with a printed register, tries to match descriptions to physical items, and returns with a stack of annotated sheets. The exercise takes weeks, disrupts operations, and the results are unreliable — because the people doing the verification often have no idea what they are looking at.
There is a simpler question to ask: why not ask the person who actually uses the asset?
The department head who uses a projector daily knows whether it works. The lab technician who operates an instrument knows whether it is in the lab. The IT administrator who issued a laptop knows whether it was returned. These custodians have the information the finance team is trying to collect — but traditional verification bypasses them entirely.
Self-declaration inverts the process. Instead of sending auditors to find assets, the system asks custodians to confirm what they have. This article explains how structured self-declaration works, when to use it, and how it fits alongside physical verification for statutory compliance.
1. The Problem — Why Centralised Verification Struggles to Scale
Centralised physical verification works reasonably well for small organisations — a single building, a few hundred assets, one person who knows where everything is. It breaks down as the organisation grows:
- The verification team does not know the assets. A finance executive sent to verify laboratory equipment cannot distinguish between a spectrophotometer and a colorimeter without reading serial numbers — and the serial number plate is often inaccessible, faded, or missing.
- Custodians are not available. The verification team arrives at a department, but the HOD is in a meeting, the lab is locked, or the staff member who manages the equipment is on leave. The team marks the asset as "could not verify" and moves on.
- Location data is stale. The register says the asset is on the 3rd floor, but it was moved to the 2nd floor six months ago. Nobody updated the register because there is no process for tracking transfers.
- The exercise is annual. Assets go missing in January but the verification happens in March. By the time the discrepancy surfaces, investigation is difficult — nobody remembers what happened three months ago.
- No condition data. Traditional verification confirms presence (yes/no) but rarely captures condition. An asset that is present but non-functional appears the same as a working asset on the verification report.
For universities with thousands of assets across multiple campuses, hospitals with equipment in every ward, or manufacturing units with tools spread across shifts — centralised verification becomes a formality that satisfies the auditor but does not actually tell management what they own.
2. What Self-Declaration Changes
Self-declaration shifts the burden of proof from the finance team to the asset custodian. The custodian is the person recorded as the asset's owner or user in the asset register. When a self-declaration campaign is launched, each custodian receives a list of assets assigned to them and is asked to confirm:
- Is the asset present? Can the custodian physically see it?
- What condition is it in? GOOD, FAIR, POOR, DAMAGED, or NOT_FOUND.
- Any remarks? Free-text context — "moved to Room 204", "sent for repair on 15 March", "screen cracked but functional".
This works because the custodian already has the information. They do not need to go looking for the asset — they see it every day. The declaration takes seconds per asset, not the minutes or hours that a visiting verification team would spend.
3. How a Structured Self-Declaration Campaign Works
3.1 Creating the Campaign
The finance or admin team defines the scope using AND-combined filters:
| Filter | Example | Effect |
|---|---|---|
| Department | Computer Science | Only assets assigned to CS department |
| Location | Building A | Only assets with location_l1 = Building A |
| Classification | FIXED_ASSET | Only fixed assets (excludes consumables, inventory) |
All filters are combined with AND — so "Computer Science + Building A + FIXED_ASSET" includes only fixed assets in the CS department located in Building A. A due date is set, and all matching active assets are stamped as PENDING.
3.2 Custodians Respond
Each custodian sees their pending assets — sorted by due date — and declares each one. Declarations can be submitted individually or in bulk (with per-item error handling, so one bad entry does not block the rest). Only the asset's registered owner can declare — preventing one person from declaring on behalf of another without accountability.
3.3 Tracking Progress
The campaign dashboard shows real-time counts: declared, pending, and overdue. The finance team can identify which departments are lagging and follow up before the deadline. This is fundamentally different from centralised verification, where the finance team has no visibility until the printed sheets come back.
3.4 Handling Non-Response
When the deadline passes, the admin can complete the campaign. Remaining PENDING assets are marked OVERDUE. Crucially, custodians can still declare overdue assets — the system does not lock them out. This creates a documented record of late compliance without permanently blocking the process.
3.5 Campaign Close and Reporting
The closed campaign produces a structured report: total assets in scope, how many were declared (with condition breakdown), how many are overdue, and who has not responded. This report can be presented to auditors as evidence of a systematic verification exercise — far more convincing than a stack of annotated printouts.
4. When to Use Self-Declaration vs Physical Verification
Self-declaration does not replace physical verification — it complements it. Each approach suits different situations:
| Approach | Best For | Frequency |
|---|---|---|
| Self-Declaration | Routine confirmation — quarterly or monthly checks, interim audits, department-level accountability | Monthly / Quarterly |
| Physical Verification (QR scan campaigns) | Year-end statutory compliance, high-value asset audits, insurance valuation exercises | Annually |
| Both combined | Self-declaration identifies which assets need closer inspection; physical verification confirms the exceptions | Rolling |
The practical pattern is: run self-declaration quarterly to maintain a baseline, then use the results to focus the annual physical verification on assets that were reported as DAMAGED, NOT_FOUND, or overdue. This reduces the scope and cost of the physical exercise substantially.
5. Condition Reporting — Beyond Presence
Traditional verification asks a binary question: is the asset there or not? Self-declaration asks a richer question: what state is it in?
| Condition | What It Means | What Happens Next |
|---|---|---|
| GOOD | Fully operational, no issues | No action needed |
| FAIR | Operational with minor issues | Note for next maintenance cycle |
| POOR | Functional but needs attention | Maintenance request or replacement planning |
| DAMAGED | Not fully functional | Repair request, insurance claim, or write-off consideration |
| NOT_FOUND | Custodian cannot locate the asset | Investigation → write-off requisition if unresolved |
This condition data feeds directly into the asset register. When a custodian reports an asset as DAMAGED, the finance team sees that status alongside the book value, depreciation schedule, and insurance coverage. This creates a direct link between operational reality and financial records — something that a printed verification checklist cannot provide.
6. Audit Trail — Every Declaration Is Permanent
Each self-declaration creates an immutable record containing the custodian's identity, timestamp, condition reported, and any remarks. These records cannot be edited or deleted after submission. For any asset, the full declaration history is available — showing every campaign the asset participated in, what condition was reported, and by whom.
The value of self-declaration for auditors is not just that it confirms asset existence — it creates a documented chain of custodian accountability. Each person who declared an asset as GOOD is on record. If the asset later turns out to be missing, the investigation starts with a specific person and a specific date.
7. Practical Considerations
7.1 Rolling vs All-at-Once Campaigns
Launching a self-declaration for all 5,000 assets across every department on the same day creates a spike of activity and a flood of follow-up queries. A rolling approach — one department per week, or one building per month — spreads the load and gives the finance team time to investigate issues as they surface.
7.2 Linking to Write-Off and Disposal
An asset reported as NOT_FOUND in two consecutive declaration campaigns is a strong candidate for write-off. The declaration history provides the evidence trail: "custodian reported NOT_FOUND on 15 January and again on 15 April — investigation confirmed the asset cannot be located." This documented trail supports the write-off requisition and satisfies the auditor's need for evidence that the asset was genuinely searched for.
7.3 Getting Custodians to Actually Respond
The biggest practical challenge with self-declaration is participation. Three things help:
- Keep it simple. The custodian should be able to declare an asset in under 10 seconds — select condition, optionally add a remark, submit. Bulk declaration for custodians with many assets.
- Visible deadlines. The system shows pending and overdue counts. Department heads can see which of their staff have not responded.
- Escalation path. When the campaign report shows 30% non-response from a department, that data point goes to the department head. Social accountability drives participation more effectively than repeated emails.
8. Frequently Asked Questions
What is the difference between physical verification and self-declaration of assets?
Physical verification involves a dedicated team walking through locations to physically locate and inspect assets. Self-declaration inverts this — the person who actually uses the asset confirms its existence, location, and condition through a system. Physical verification is thorough but slow, expensive, and disruptive. Self-declaration is faster and scales better because it distributes the work to the people who already know where the assets are. Many organisations use both: self-declaration for routine quarterly checks, and physical verification campaigns for year-end statutory compliance.
Is custodian self-declaration accepted by statutory auditors?
Self-declaration alone does not replace the physical verification requirement under CARO 2020 or Companies Act 2013. However, it serves as a strong supplementary control. When each declaration is timestamped, tied to a specific user, and recorded with condition details, it creates an evidence trail that auditors can rely on for interim checks. For year-end compliance, organisations typically combine self-declaration data with a targeted physical verification campaign — the self-declaration identifies which assets need closer inspection, reducing the scope and cost of the physical exercise.
What happens if a custodian does not respond by the deadline?
Assets that remain in PENDING status after the due date are automatically flagged as OVERDUE. The finance team can see which custodians have not responded and which assets are overdue. Custodians can still submit declarations for overdue assets — the system does not lock them out. When the admin closes the campaign, any remaining PENDING items are marked OVERDUE in the final report. This creates a documented record of non-compliance that can be escalated to department heads.
Can self-declaration be scoped to specific departments or locations?
Yes. Declaration requests are created with AND-combined scope filters — department, location, and classification. Only assets matching all specified criteria are assigned to the campaign. For example, a request scoped to "IT department + Building A" will only include IT assets located in Building A. This allows rolling campaigns — one department per week, or one location per month — rather than disrupting the entire organisation at once.
What condition options can custodians report?
Custodians select from five condition states: GOOD (fully operational), FAIR (operational with minor issues), POOR (functional but needs attention), DAMAGED (not fully functional, repair needed), or NOT_FOUND (asset cannot be located). Each declaration can include free-text remarks for context. The condition data feeds into the asset register — an asset reported as DAMAGED can trigger a maintenance request, while NOT_FOUND triggers an investigation workflow that may lead to a write-off requisition.