TL;DR
Equipment depreciation is an accounting exercise built on an operational record, and the operational record is usually wrong. Finance needs to know what exists, what it cost, when it arrived and when it stopped being used. IT tends to know the first three and almost never the fourth. The gap shows up as devices depreciating on the books years after they went in a cupboard.
- Depreciation is only as good as the disposal date, and nobody records it.
- A device in a drawer is still on the books until somebody says otherwise.
- Finance needs four fields, not a full asset management platform.
- Treatment differs by country and asset class. Ask your own accountants.
- Reconcile quarterly, not annually. An annual gap is too big to investigate.
- Write the retirement trigger into the offboarding process, not the audit.
Why equipment depreciation drifts from reality
Depreciation spreads the cost of an asset across the period it is useful. That is straightforward arithmetic once you know three dates and one number.
The difficulty is never the arithmetic. It is that the fleet changes constantly and the register does not.
Best tools for Device Management
A laptop gets reassigned. Another is damaged and quietly replaced. A third goes home with somebody who left in March and nobody noticed until October. None of those events reaches finance, so the schedule keeps depreciating assets that no longer do any work.
What that costs
Two things, neither dramatic on its own. The balance sheet carries value that is not there, and the replacement budget is built on a fleet size that is wrong.
The second is the one that bites operationally. If the register says 340 laptops and 300 exist, the refresh forecast is overstated by forty machines and the budget conversation starts from fiction.
The four fields finance actually needs
Finance teams rarely want an asset management platform. They want four columns that are true.
| Field | Who holds it | How often it is wrong |
|---|---|---|
| Acquisition date | Procurement or the invoice | Rarely |
| Cost | Finance already has it | Rarely |
| In-service date | IT, at provisioning | Sometimes, if kit sits in stock |
| Disposal or retirement date | Nobody | Almost always |
The pattern is clear enough that it is worth stating plainly. The first two are captured because money moved. The third is captured because somebody set the device up. The fourth is captured only if a process forces it.
Why the disposal date is special
Every other field is created by an event somebody already wanted to do. Retirement is created by an event nobody wants to do, usually at the least convenient moment, often by somebody who has already left.
So it has to be forced by a process rather than left to diligence. The place to force it is offboarding, which is the one moment the company reliably pays attention. Our note on unreturned equipment covers what happens when that step is missing.
Useful life, and the number people copy
Most companies use three years for laptops because somebody used three years once. It is a reasonable default and it is worth checking against your own evidence.
The honest version is that useful life varies by role. A developer machine under constant load and a finance laptop used for spreadsheets and video calls do not wear at the same rate, and treating them identically overstates one and understates the other.
How that is treated for tax is a separate question from how it is treated internally, and the two frequently differ. IRS Publication 946 on depreciating property sets out the United States position on depreciating property, and the UK guidance on capital allowances covers capital allowances in the UK. Both are worth reading with your own accountants rather than applied from a blog, including this one.
The practical split
Many teams run two numbers: a tax treatment that follows local rules and an internal refresh assumption that follows observed failure and performance. Those serve different purposes and there is no reason they should match.
For how the refresh side of that is set, see our piece on choosing a hardware refresh cycle.
Reconcile quarterly, not annually
An annual reconciliation sounds proportionate and behaves badly. Twelve months of drift produces a gap too large to investigate, so it gets written off in a block and nothing is learned.
Quarterly gaps are small enough to chase individually, which is what makes them useful. If eleven devices are unaccounted for, somebody can actually find out what happened to eleven devices.
- Export the register and the live device list from whatever manages your endpoints.
- Match on serial number, not on assigned user, because people change and serials do not.
- Investigate the difference in both directions. Devices on the register and not in the fleet, and devices in the fleet and not on the register.
- Record a disposal date for anything confirmed gone, and feed it back.
The second direction catches more than people expect. Devices bought on an expense claim, replacements shipped directly by a vendor, machines inherited in an acquisition. All real, none on the register.
What to do with the gap you find
Resist the urge to write the whole difference off in one line. Split it into three buckets: confirmed disposed, confirmed in use but unrecorded, and genuinely unknown.
The first two are corrections and take minutes each. Only the third is a loss, and it is usually far smaller than the raw gap suggests. Reporting the raw gap as shrinkage makes the problem look worse than it is and tends to trigger a tooling purchase that would not have been needed.
Record how many devices land in each bucket. Over three or four quarters that split tells you whether the process is improving, which a single headline number never does.
The decision table
Where to start depends on which half is broken.
| Situation | Scale | Setup | Primary pain | Recommended starting point |
|---|---|---|---|---|
| No register at all | Under 50 staff | Spreadsheet, maybe | Nobody knows the fleet size | One reconciliation, then a disposal trigger |
| Register exists, never updated | 50 to 200 | Tooling in place | Disposal dates missing | Fix offboarding before buying anything |
| Finance and IT disagree | Any | Two systems, two truths | Argument every quarter | Match on serial, agree one source |
| Devices inherited in an acquisition | Series B+ | Two fleets, two registers | Nothing reconciles | Treat the acquired fleet as a fresh baseline |
| Heavy remote workforce | Any | No physical audit possible | Cannot see what exists | Reconcile against endpoint check-in data |
Row five is where most distributed companies sit, and it is the reason a physical stock count is not the answer. The nearest equivalent is the last time each device contacted your management tooling.
Closing the loop at disposal
A retirement date is only trustworthy if something actually happened to the device.
Three endings, and each needs a different record. Resold, in which case there is proceeds data finance wants. Recycled, in which case there should be a certificate. Lost, in which case somebody should write that down honestly rather than leaving the row open forever.
the EPA guidance on electronics stewardship covers electronics stewardship and why the disposal route matters beyond the accounting. For the environmental reporting side, our piece on equipment and ESG reporting goes further.
Where a partner helps
For distributed teams the hard part is not the paperwork, it is physically getting the device back before any of this can be recorded. RemoAsset handles retrieval from remote employees and can hold recovered stock until it is reissued or disposed of, which turns an open row into a dated one.
Whatever route you use, the rule is the same: no device leaves the fleet without a date and a reason attached.
RemoAsset recovers and holds devices so disposal dates are real rather than estimated. More on asset records at HROpsLab.
Frequently asked questions
What does finance need from IT for equipment depreciation?
Four fields that are actually true: acquisition date, cost, in-service date and disposal date. The first two usually exist because money moved, and the third usually exists because somebody set the device up. The fourth is the one that is almost always missing, because retiring a device is an event nobody wants to do and often falls to somebody who has already left. That single missing date causes most depreciation drift.
How long should we depreciate laptops over?
Three years is the common default and it is worth testing against your own failure and performance data rather than inherited. Useful life genuinely varies by role, since a machine under constant build load and one used for spreadsheets do not wear at the same rate. Tax treatment is a separate question that depends on your jurisdiction and how the asset was acquired, so take that from your accountants and the primary guidance, not from an article.
Why does our asset register never match the real fleet?
Because the register is updated by events people want to do and the fleet changes through events they do not. Purchases get recorded because there is an invoice. Reassignments, quiet replacements and devices that left with a departing employee generate no paperwork at all. The gap compounds, so the register overstates the fleet, which in turn overstates the refresh budget built on top of it.
How often should we reconcile the asset register?
Quarterly. Annual reconciliation sounds proportionate and behaves badly, because twelve months of drift produces a difference too large to investigate, so it gets written off in a block and nothing is learned. A quarterly gap of ten or fifteen devices is small enough that somebody can actually find out what happened to each one, which is the only version that improves the process.
Should we match devices on user or serial number?
Serial number. People change teams, change names, leave and return, and any of those breaks a match keyed on the assigned user. Serial numbers do not change. Match in both directions while you are at it, because devices present in the fleet but absent from the register are more common than expected, usually arriving through expense claims, direct vendor replacements or an acquisition.
What should happen when a device is finally disposed of?
Record a date and a reason, and make sure something actually happened to the hardware. Resold gives finance proceeds data. Recycled should produce a certificate. Lost should be written down honestly rather than leaving the row open indefinitely. The rule worth adopting is that no device leaves the fleet without a date and a reason attached, which is what makes the depreciation schedule trustworthy.
How do we audit a fleet we cannot physically see?
Use the last time each device checked in to your endpoint management tooling as the practical equivalent of a stock count. A physical audit is not available to a distributed company, and waiting until devices come back to an office means waiting indefinitely. Check-in data tells you what is alive, and anything that has not reported for a long period is a candidate for investigation rather than an assumption of loss.