A first-time fixed asset verification rarely begins with a register that looks obviously wrong.

The finance team usually hands over a Fixed Asset Register (FAR) that has been maintained for years. Additions have been recorded, depreciation has been calculated, and the closing numbers have gone through successive financial periods.

Then the verification team starts walking the floor.

Assets are found at locations different from the register. Some cannot be identified from their descriptions. Some records point to assets that nobody can locate. Other assets are physically present but cannot be traced back to a register line.

The variance list can be longer than expected.

This happens because physical assets do not remain static. They move between users, departments and locations. They are repaired, replaced, transferred, scrapped and sometimes renamed by the people who actually use them.

Over time, the physical reality can move away from the register.

A first-time verification is where that accumulated difference becomes visible.

What does the Fixed Asset Register look like before verification starts?

The first challenge often appears before anyone counts an asset.

It is the quality of the register itself.

A FAR can be perfectly usable for accounting purposes and still be difficult to use for physical verification. Accounting records and physical identification do not always require the same information.

From our first-time verification exercises, poor asset descriptions are one of the first and most recurring issues we encounter.

And that matters more than it may initially appear.

Poor descriptions turn verification into identification

Consider a register description such as:

“Computers – 50 Nos.”

That may tell the accounts team what was capitalised. It does not tell a verification team which 50 computers those records represent.

The same problem occurs with descriptions such as:

• Machine
• Tool
• Equipment
• Furniture
• Electrical item
• Computer accessory
• Plant equipment

When the description is too generic, physical verification stops being a straightforward matching exercise.

It becomes an identification exercise.

The team has to use whatever other information is available — serial number, make, model, purchase information, location, department, existing tag, technical characteristics or discussions with the people using the asset — to establish which physical asset belongs to which FAR record.

That distinction is important.

Before you can verify an asset, you first have to know which asset you are verifying.

This additional identification work is one reason a first-time verification is different from a subsequent cycle where the asset base has already been cleaned and individually identified.

Plant & Machinery and tools create some of the hardest matching problems

From our field experience, Plant & Machinery and tools are among the asset categories where description-based matching becomes particularly difficult.

With many IT assets, a manufacturer’s serial number, model number or another unique identifier may be available.

Plant & Machinery can be different.

The description in the FAR may have originated from an invoice, purchase order or accounting classification. The production or maintenance team may know the same asset by a completely different name.

The FAR may call something by its purchased description.

The operator may call it by its function.

The maintenance team may use another name.

And the physical machine may carry a manufacturer’s plate containing yet another description.

The asset can therefore be physically standing in front of the verification team and still not be easy to match with the FAR.

Tools create a similar problem. Several items may look alike, descriptions may be generic, and individual identification may not have formed part of the original capitalisation process.

This is where verification becomes much more than counting.

One FAR line can represent many physical assets

Another issue is quantity-based capitalisation.

A single FAR line may represent 10 chairs, 20 laptops, 50 tools or several pieces of equipment.

Accounting may require only one capitalised line.

Physical verification does not work that way.

There may be 50 separate physical items on the floor.

If those items need individual accountability, the verification exercise has to establish how one accounting line relates to multiple physical units.

This becomes particularly important where individual asset tags are to be applied.

The accounting record may remain one parent line, while the physical exercise requires identifiable individual units underneath it.

Accounting locations are not always physically usable locations

A register may say:

HO

Plant

Admin

Warehouse

Those descriptions may have made perfect sense when the records were created.

But they may not be enough for someone trying to locate an asset several years later.

A plant can contain multiple buildings, production lines, departments and stores. An office can contain several floors and departments. A warehouse may have multiple zones.

This exposes an important difference between an accounting location and a physically usable location master.

A location field is useful for verification only when it helps someone find the asset.

First-time verification often becomes the point at which broad historical location codes are translated into locations that reflect how the organisation actually operates on the ground.

Duplicate records can survive migrations

ERP migrations and historical data transfers can leave duplicate or near-duplicate asset records.

On paper, there appear to be two assets.

On the floor, there may be one.

Without proper identification, the physical asset can be matched against the wrong record, or two similar FAR records may appear capable of matching the same asset.

This is one reason quantity agreement alone is not enough.

The question is not simply:

“Do we have ten?”

It is also:

“Can we establish which ten FAR records correspond to these ten physical assets?”

Serial numbers are missing where they matter

For many types of equipment, the manufacturer’s serial number is one of the strongest identifiers available.

Yet the FAR may not contain it.

This becomes particularly important for laptops, desktops, servers, printers, specialised equipment and machinery where several assets can have similar descriptions.

A description such as “Laptop” or even a particular laptop model identifies a type of asset.

It does not necessarily identify that particular asset.

A first-time verification creates an opportunity to capture these identifiers and strengthen the register for subsequent cycles.

CWIP and completed assets do not always tell the same story

Capital Work in Progress creates another type of identification issue.

The records may indicate that something remains under CWIP, while the field team finds equipment that appears to have been installed or put to use.

That finding does not, by itself, determine the accounting treatment. But it raises a question that needs to go back to finance.

The reverse situation also occurs.

Capitalised assets can still be lying in stores

An asset may appear as capitalised in the records but be found packed, unused or lying in a store rather than installed at its intended operating location.

The FAR tells you that the asset has been recorded.

The floor tells you what is actually happening with it.

This is one of the reasons physical verification adds information that cannot be obtained simply by reviewing the register.

What actually comes back from the floor?

Once verification begins, the FAR stops being only a spreadsheet.

Every line has to meet something physical.

That is where the findings start.

Assets in the FAR that cannot be found

These are commonly described as “not found” assets or, in some contexts, ghost assets.

But “not found” should be treated as a verification finding requiring investigation — not automatically as proof that the asset is missing.

The asset may have been:

• transferred to another location
• disposed of without the FAR being updated
• scrapped
• moved to another department
• recorded under an unusable description
• replaced while the old FAR record remained active

The physical exercise establishes that the team could not match the FAR record with an asset at the expected location.

What happened to the asset is a reconciliation question.

Verification identifies the exception. Reconciliation explains it.

Assets are found physically but cannot be found in the FAR

The reverse is equally important.

The team finds an asset on the floor but cannot establish a corresponding FAR record.

That does not automatically mean the asset was never capitalised.

It may be:

• included within a quantity-based FAR line
• recorded under a different description
• recorded at another location
• part of a transfer that was not reflected completely
• associated with another asset record
• an item whose capitalisation trail needs to be traced

Again, the physical finding should not immediately be converted into an accounting conclusion.

It should be investigated.

The asset exists, but the location is wrong

Location mismatches arise where assets move but the register does not move with them.

IT equipment may move with employees. Furniture may move between departments. Equipment can shift between production areas. Assets may be temporarily transferred to another site.

The asset exists.

The FAR record exists.

But the two disagree about where the asset is.

That difference matters because location information affects custody, accountability, insurance, future verification and the usefulness of the asset register itself.

The asset exists, but it cannot be uniquely identified

Sometimes the physical quantity broadly agrees with the register, but there is no reliable way to establish which physical item corresponds to which FAR record.

This is an identification gap.

Ten similar assets may physically exist, and the FAR may also contain ten records.

But that does not necessarily mean the ten have been individually reconciled.

Without a unique identifier, the organisation may know that the quantity exists without knowing which record belongs to which physical asset.

That is where tagging can fundamentally change the next verification cycle.

Disposals remain in the register

An asset may have been disposed of correctly on the ground, but the FAR was never updated.

The verification team naturally cannot find it.

It appears in the initial results as “not found.”

But after investigation, the real conclusion may be very different:

The asset is not missing; the register is outdated.

That distinction matters to management.

A good physical verification exercise should therefore not end with a list of “found” and “not found” assets.

The exceptions need to move into reconciliation.

Condition information appears that the FAR never contained

The register may say that an asset exists.

The floor may show that it is damaged, idle, dismantled, obsolete, under repair or no longer being used.

That information often does not exist in an accounting FAR because the register was never designed to capture it.

Physical verification adds an operational layer to the asset information.

And in some cases, that operational information may require further consideration by finance or management.

We stopped treating description matching as a purely manual exercise

Poor descriptions create another problem when the exercise reaches reconciliation.

The physical team may have described an asset using the terminology visible on the floor, while the FAR contains terminology originating from an invoice or an old accounting record.

Manually reading thousands of descriptions and searching for possible matches can become difficult.

We have therefore developed internal tools to assist with reconciliation and description matching. We have also used AI-assisted matching to identify possible relationships between differently worded FAR and physical descriptions for further review.

But there is an important distinction.

A suggested match is not a verified match.

Technology can help narrow down the possible relationships. It can identify descriptions that may refer to the same asset and reduce the amount of purely manual searching.

The proposed match still needs to make sense against the information available from the verification exercise.

That can include serial number, make, model, location, department, asset characteristics, existing identification and other supporting information.

Technology assists the search.

The verification evidence determines the match.

The findings that can surprise the finance team

Some differences are expected before the exercise starts.

Others become visible only because somebody physically went to the location.

A substantial asset exists but cannot be traced to the FAR

The team may find a significant physical asset operating at the location but be unable to trace it to an identifiable FAR record.

The immediate question is not simply, “Why wasn’t this counted before?”

It is:

Where did this asset come from, and how was it accounted for?

That may require tracing purchase records, transfers, project costs, capitalisation records or other supporting information.

One physical asset appears capable of matching more than one FAR record

Without unique identification, two similar FAR records may both appear capable of matching the same physical item.

The quantities can look reasonable until the matching is performed at an asset level.

This is the difference between counting and identification.

The FAR says one location. The asset says another.

An asset can remain assigned to Head Office in the register long after it has moved to another operating location.

Nothing may be wrong with the gross block.

Nothing may be wrong with depreciation.

But the asset master no longer reflects reality.

Physical verification exposes that difference because it tests the location against the floor rather than assuming the master is current.

Idle assets become visible

A FAR cannot tell you everything about how an asset is being used.

Physical verification can reveal equipment that exists but is idle or unused.

That may not create an accounting variance, but it can still be useful management information.

Knowing what exists, where it exists and its observed condition can support decisions beyond the reconciliation itself.

What do these findings mean for the financial records?

Physical verification does not determine the accounting treatment of every exception.

But the findings can identify areas that require financial review.

For example:

• Gross block may require review where disposals have taken place but the FAR remains unchanged.
• Depreciation records may require review where assets that no longer exist continue to remain active in the register.
• Insurance schedules may need comparison with the verified asset base.
• Condition findings may identify assets requiring management consideration for impairment or useful-life assessment.
• CWIP or capitalisation records may require review where the physical status of an asset differs from its recorded status.

The important point is:

The physical finding is the beginning of the accounting question, not automatically the accounting answer.

This is why physical verification, FAR reconciliation and FAR-to-General-Ledger reconciliation work better when they are connected rather than treated as unrelated exercises.

What should a good first-time verification leave behind?

The value of the first exercise is not only the variance report.

Done properly, it creates a better starting point for every verification that follows.

Depending on the scope of the exercise, the organisation can come out with:

• a physically validated asset base
• individual identification for assets where tagging is appropriate
• improved asset descriptions
• updated location information
• custodian or department information where captured
• serial numbers and other identifiers
• condition information
• a documented list of unmatched and exception items
• reconciliation explanations and actions

This changes the nature of the next verification.

During the first exercise, a significant part of the effort can go into answering:

“What is this asset?”

Once an asset has been identified correctly, linked to the appropriate FAR record and tagged where appropriate, the next cycle can increasingly focus on:

“Is this the same asset, and is it where the register says it should be?”

That is a very different exercise.

The first cycle builds the identification base.

The later cycles use it.

Why does the Fixed Asset Register drift from reality?

A FAR does not usually drift because of one large event.

It happens one movement at a time.

A laptop moves with an employee.

A chair moves to another floor.

A machine shifts within a plant.

A tool changes department.

An old asset is scrapped but the information does not reach the person maintaining the FAR.

A new asset is capitalised under a generic description.

A location changes its name.

Data moves from one ERP to another.

Individually, these may appear to be small events.

Over time, they accumulate.

That is why periodic physical verification matters. It brings the accounting record back into contact with the physical world it is intended to represent.

The first verification creates the baseline

A first-time fixed asset verification can produce uncomfortable questions.

That is part of its value.

It establishes what exists, where it exists, what can be matched to the Fixed Asset Register and what still requires investigation.

But its longer-term value is the baseline it creates.

Poor descriptions can be improved. Locations can be corrected. Serial numbers can be captured. Assets can be individually identified. Appropriate assets can be tagged. Exceptions can be reconciled rather than simply carried forward.

The next verification therefore does not have to start from the same uncertainty.

The first exercise is often doing identification work. The next exercise can start from an asset base where much of that identification has already been done.

Tag My Assets undertakes physical verification, asset tagging and FAR reconciliation assignments across different operating environments.

The objective is straightforward:

Connect the asset on the floor with the asset in the register — and make the difference between the two clear enough to investigate and resolve.

---

Frequently Asked Questions

What does a first-time fixed asset verification usually find?

A first-time verification can identify poor asset descriptions, assets that cannot be located, physical assets that cannot be matched to the FAR, location differences, duplicate or unclear records, missing identification information, condition issues and disposals that were not updated in the register.

The nature of the findings depends on the organisation, its asset classes and the quality of the existing Fixed Asset Register.

What is a ghost asset?

A ghost asset generally refers to an asset that continues to appear in the Fixed Asset Register but cannot be physically located.

However, a “not found” result should be investigated before concluding that the asset is actually missing. It may have been transferred, disposed of, scrapped or recorded using information that no longer allows it to be identified.

How many assets are typically not found during verification?

There is no responsible universal percentage.

The result depends on factors such as the quality and age of the FAR, asset mobility, previous verification practices, disposal controls, locations and the types of assets involved.

A first-time verification should establish the organisation’s actual position rather than begin with an assumed variance percentage.

Why does the Fixed Asset Register drift from reality?

Assets move, users change, locations change, disposals occur and new assets are added throughout the year.

If every physical change is not reflected in the FAR at the same time, small differences accumulate. Periodic physical verification identifies those differences and provides a basis for updating and reconciling the records.

What happens to assets found on site but not in the register?

They should first be recorded as verification exceptions and investigated.

Purchase records, invoices, transfer records, capitalisation details and other available information may need to be checked before deciding whether an asset is genuinely unrecorded, included within another FAR line or requires some other register or accounting correction.

---