TL;DR
Fixed asset management software exists to satisfy finance, and your IT register exists to satisfy operations. They describe the same laptops and they almost never agree, because they are updated by different people at different moments for different reasons.
- Two registers, two owners, two different purposes.
- They disagree because they are updated at different moments.
- Finance needs value and dates; IT needs state.
- Disposal is where the gap becomes visible.
- Reconcile on a schedule, not during an audit.
- Pick one system of record per field.
Why there are two of them
Not duplication for its own sake. They were built for different readers.
The finance register exists to support the accounts: what was bought, when, at what value, over what useful life, and what has been disposed of. It is updated when an invoice is processed.
Best tools for Device Management
The IT register exists to support operations: what is enrolled, patched, assigned and reachable. It is updated when a device is deployed, or ideally continuously.
Both are correct from their own point of view and they diverge immediately, because a laptop is bought weeks before it is issued and it stops being used long before anybody disposes of it formally.
The simplest illustration
A machine that broke and was replaced. IT closed its record the day it stopped working. Finance still carries it at a written-down value because no disposal was recorded. Both systems are behaving correctly and the company has one laptop and two different truths.
Decide which system owns which field
This is the whole fix and it takes one meeting.
Go through the fields and assign each to exactly one system of record. Everything else copies from there.
Finance owns acquisition date, purchase value, depreciation basis, net book value and disposal date. IRS Publication 946 on depreciating property sets out what depreciation involves and why those fields are not optional.
IT owns serial number, assigned person, location, configuration state and last seen date.
The two overlap on exactly one thing that matters: whether the device still exists. That is the field to reconcile, and it is the one neither system owns naturally.
| Field | Owner |
|---|---|
| Acquisition date and value | Finance |
| Depreciation and net book value | Finance |
| Serial number | IT |
| Assigned person and location | IT |
| Still exists | Reconciled, not owned |
Disposal is where the gap shows
And it is the most expensive place for it to show, because it shows during an audit.
A device is wiped, collected and recycled. IT closes its record. If no disposal is recorded in the finance system, the asset stays on the books at a written-down value and the accounts carry something that does not exist.
The reverse also happens. Finance writes assets off at the end of a useful life while the machines are still in use, so the register says zero and forty people are working on them.
Neither is a software failure. Both are a process gap: nobody told the other system.
the EPA on electronics and batteries management covers the handling side of disposal and NIST Special Publication 800-88 on media sanitization is the sanitization standard the evidence is judged against. The practical requirement is that whoever disposes of a device produces one document that both systems are updated from, rather than each being told separately or not at all.
Reconcile on a schedule
Quarterly is usually enough and it is far cheaper than doing it once a year under pressure.
Four steps. Export both registers on the same day. Match on serial number, which is the only field both should hold reliably. List the rows that appear in one and not the other. Then resolve each exception by deciding which system is wrong and correcting it.
That last step is the one that gets skipped, and skipping it means you have produced a list of discrepancies rather than a reconciliation.
Expect three recurring exception types: devices disposed of in IT and not in finance, devices written off in finance and still in use, and devices in finance that IT has never seen because they were never enrolled.
an asset management policy covers the policy that makes this somebody’s job rather than an annual scramble.
Can one system do both?
Sometimes, and it is worth testing rather than assuming either way.
Some IT asset tools hold acquisition value, depreciation and disposal fields well enough that finance will accept them. Some finance systems have an asset module that can carry a serial number and an assigned person.
The test is not whether the fields exist. It is whether the team that needs the output will actually use the system. Finance will not log into an IT console monthly, and IT will not update an accounting package every time a laptop moves desks.
So the realistic answer for most companies is two systems and a reconciliation, with one agreed export format between them. IT asset management software covers the IT side of that choice.
What to do about devices in neither register
Every company has some, and they surface during the first proper reconciliation.
A laptop bought on somebody’s card and expensed. A machine inherited in an acquisition. A device sent by a client for a project. None went through procurement, so finance has no asset record, and none was enrolled, so IT has no row either.
Add them deliberately with whatever is known, flagged as retrospective, rather than leaving them off because the history is incomplete. A device you cannot value is still a device you are responsible for, and the flag is what stops an incomplete record being mistaken for a clean one.
The question that settles it
Who will do the data entry, and is it part of something they already do? A single system that nobody updates is worse than two that are reconciled quarterly.
Why this reaches HR at all
Because the moments that break both registers are HR moments.
Somebody joins and a device is issued. Somebody leaves and it should come back. Somebody changes role and the machine moves. Somebody is on long-term leave and the device sits unused and unreported.
At each of those points a record needs updating, and HR is the only function that reliably knows the event happened. IT finds out late and finance later still.
The practical answer is to attach the register update to the joiner and leaver process rather than leaving it as a separate task. writing an employee equipment policy covers the policy framing, and the mechanism matters more than the wording: a checklist item inside a process that already runs will be done, and a reminder will not.
The register is not the recovery
The gap that makes all of this academic if it is not covered.
Reconciling two registers tells you precisely what is missing. It does not bring anything back. A company can have immaculate records of hardware it will never see again.
The recovery work is physical: collecting from people who have left, shipping across borders, storing between employees, and disposing with evidence. RemoAsset publishes 80+ countries for procurement and 25+ for retrieval, and RemoAsset’s laptop lifecycle management covers the lifecycle.
Where devices are genuinely unrecoverable, the honest step is a deliberate write-off with a date and a reason rather than leaving rows open indefinitely. An open row implies a device that might come back, and after a certain point that is a claim neither register should be making.
the NIST Cybersecurity Framework is a reasonable frame for presenting the whole picture to a board, since it separates the record from the control. Those two get conflated constantly, and a company with excellent records and no recovery process tends to believe it is in better shape than it is.
Reconciled records still need the hardware back. RemoAsset retrieves across 25+ countries. See RemoAsset’s laptop lifecycle management or RemoAsset’s pricing.
Frequently asked questions
Why do we need fixed asset management software and an IT register?
Because they were built for different readers. The finance register supports the accounts: what was bought, when, at what value, over what useful life, and what has been disposed of, updated when an invoice is processed. The IT register supports operations: what is enrolled, patched, assigned and reachable, updated when a device is deployed. Both are correct and they diverge immediately.
How should we decide which system owns what?
Assign each field to exactly one system of record and copy everything else from there. Finance owns acquisition date, purchase value, depreciation basis, net book value and disposal date. IT owns serial number, assigned person, location, configuration state and last seen date. The two overlap on one thing that matters, whether the device still exists, which is what you reconcile.
Where does the gap usually show?
At disposal, and usually during an audit. A device is wiped, collected and recycled and IT closes its record, but if no disposal is recorded in finance the asset stays on the books at a written-down value. The reverse happens too: finance writes assets off at the end of a useful life while the machines are still in use. Neither is a software failure.
How often should we reconcile?
Quarterly is usually enough and far cheaper than doing it once a year under pressure. Export both registers on the same day, match on serial number since that is the only field both should hold reliably, list rows appearing in one and not the other, then resolve each exception by deciding which system is wrong. That last step is the one that gets skipped.
Can one system do both jobs?
Sometimes, and it is worth testing rather than assuming. Some IT asset tools hold acquisition value, depreciation and disposal fields well enough that finance will accept them. The test is not whether the fields exist but whether the team needing the output will use the system, since finance will not log into an IT console monthly and IT will not update an accounting package per desk move.
Why is this an HR issue?
Because the moments that break both registers are HR moments. Somebody joins and a device is issued, somebody leaves and it should come back, somebody changes role and the machine moves, somebody is on long leave and the device sits unused. HR is the only function that reliably knows the event happened, so attach the register update to the joiner and leaver process rather than leaving it separate.
What do reconciled registers not solve?
Recovery. Reconciling tells you precisely what is missing and brings nothing back, so a company can have immaculate records of hardware it will never see again. The recovery work is physical: collecting from leavers, shipping across borders, storing between employees and disposing with evidence. Where devices are genuinely unrecoverable, write them off deliberately with a date and a reason.