Asset Movement Register: A Practical Format for Better Fixed Asset Control

Summary: Article explains how fixed assets can remain physically available while being reported as “not found” during physical verification when their locations, departments or custodians change without corresponding updates to the Fixed Asset Register (FAR). It presents an Asset Movement Register as a practical control to record asset movements and create a traceable link between the physical asset and accounting records. Suggested fields include movement date, FAR code, asset description, serial number, asset tag, origin and destination locations, departments, custodians, movement type, reason, approval reference, handover details, receipt confirmation, FAR update status, tag status and remarks. The content distinguishes permanent movements from temporary, repair and return movements, noting that permanent transfers should ultimately result in FAR updates. It highlights employee transfers and differences between FAR codes, serial numbers and physical tags as common reconciliation challenges. During physical verification, movement records can help explain assets found at locations different from those recorded in the FAR. The suggested process is: movement request, approval, handover, acknowledgement, movement recording and FAR update where applicable. Periodic review is suggested for pending FAR updates, prolonged temporary movements, missing acknowledgements, unapproved movements and employee transfers.

Introduction

A fixed asset can be physically available in an organisation and still be reported as “not found” during physical verification.

This happens more often than one might expect.

A laptop recorded at the Delhi office is transferred to Gurugram. A printer moves from one department to another. Furniture is shifted when a branch is renovated. A machine is sent to another unit for temporary use. The asset moves immediately, but the Fixed Asset Register (FAR) continues to show the old location.

When physical verification takes place a few months later, the problem surfaces. The verification team looks for the asset where the FAR says it should be and cannot find it. At the receiving location, the same asset may appear as an additional item.

Nothing has necessarily been lost. The records simply did not move with the asset.

This is where an Asset Movement Register becomes useful.

What exactly should an Asset Movement Register do?

An Asset Movement Register is not meant to become another register maintained merely for compliance. Its practical purpose is to create a trail whenever an asset changes location, department or custodian.

It should answer a few basic questions: Which asset moved? Where did it move from and to? Who authorised the movement? Who received it? And, in the case of a permanent transfer, was the FAR subsequently updated?

If these questions can be answered from one controlled record, a large part of the reconciliation effort during physical verification becomes easier.

Consider a simple example. The FAR shows a laptop with Asset ID FA-1025 at the Delhi office under Employee A. The employee is transferred and the laptop is subsequently allocated to Employee B at Gurugram. The physical handover takes place, but Finance is not informed.

At the next verification, FA-1025 may be reported as short in Delhi. The laptop found in Gurugram may initially appear as an additional asset because the team cannot immediately connect it with the Delhi record.

An effective movement register would provide that missing link.

Suggested Asset Movement Register Format

There is no single statutory format that every organisation must use. The fields should depend on the nature of the assets and the way they move within the organisation.

A practical format may contain the following:

The format itself is not the difficult part. Most organisations can create such a sheet in a few minutes. The real control lies in ensuring that movements are actually recorded and that permanent movements ultimately flow back into the FAR.

Where does the process usually break?

In our experience, the problem is rarely that companies do not know an asset has moved. Someone usually knows.

The branch manager may know that the printer was shifted. IT may know that the laptop was reassigned. Administration may have arranged the movement of furniture. Security may even have a gate pass showing that a machine left the premises.

The difficulty is that these pieces of information often remain in different places. One is in an email, another in a WhatsApp message, another in a gate pass and another in someone’s memory. Finance continues to maintain the FAR based on the last information available to it.

This is why an Asset Movement Register should not become another isolated Excel file. The movement process needs to end with an update to the relevant asset master wherever the transfer is permanent.

Permanent and temporary movements need different treatment

Not every movement requires an immediate change in the FAR.

Suppose a testing instrument is sent from Plant A to Plant B for ten days and is expected to return. Changing its permanent location in the FAR may not be necessary. What is necessary is a record showing where the instrument has gone, when it went, why it was moved and when it is expected back.

The situation is different when an asset is permanently transferred to another branch or department. In that case, recording the movement without updating the FAR only postpones the problem.

A useful control is therefore to classify each movement as Permanent, Temporary, Repair, Return or Other, and include a separate field stating “FAR Updated – Yes/No.”

Finance can then periodically review permanent movements where the FAR update is still pending.

The employee transfer problem

IT assets provide one of the clearest examples of why movement controls matter.

Assume a laptop is issued to Employee A. A few months later, Employee A changes role and hands the laptop to Employee B. Both employees and their manager know about the transfer, so operationally there appears to be no problem.

But suppose the asset register still shows Employee A as the custodian.

When Employee A eventually leaves the organisation, the exit process may show a laptop outstanding against that employee. IT then has to trace the machine, speak with the old department and establish that it was transferred months earlier.

A simple movement record with acknowledgement from Employee B could have prevented the entire exercise.

For employee-held assets, therefore, a transfer should ideally not be considered complete merely because the physical handover has taken place. The new custodian should acknowledge receipt and the relevant asset record should be updated.

One asset, different identities

Another practical difficulty appears when Finance, IT and Administration identify the same asset differently.

Finance may use an FAR code. IT may use the manufacturer’s serial number. The physical asset may carry a QR or barcode tag. A branch register may describe it simply as “Dell Laptop.”

All four references may relate to the same laptop, but unless there is a common mapping between them, tracing its movement becomes unnecessarily difficult.

Where available, the movement register should therefore capture the FAR Asset ID, physical tag number and serial number together. Not every asset will have all three, but recording multiple identifiers where available makes subsequent reconciliation much easier.

This becomes particularly important for assets such as laptops, servers, electronic equipment and machinery where serial numbers provide an additional identification point.

What happens during physical verification?

The value of a movement register becomes most visible when physical verification starts.

Suppose a machine appearing in the FAR at Location A is not found there. Before treating it as a shortage, the team can check whether an approved movement exists. If the register shows that the machine was transferred to Location B three months earlier and receipt was acknowledged there, the issue is no longer simply “asset not found.”

The next question is more useful: Why was the FAR not updated?

Similarly, an asset found at a location but not appearing in that location’s FAR may be traced through recent movement records. What initially looks like an additional asset may actually be a valid inter-location transfer awaiting a master-data update.

The movement register should, however, be used to investigate differences, not to normalise them. If every verification requires dozens of movement records to explain incorrect FAR locations, the underlying update process needs attention.

Movement control should be part of the process, not an annual exercise

A common temptation is to clean up asset locations immediately before the annual physical verification. That may help the verification exercise, but it does not solve the control problem.

Asset movement happens throughout the year. The record should therefore be created when the asset moves, not several months later when somebody starts preparing for audit.

A simple workflow can be sufficient:

Movement requested → Approval obtained → Asset handed over → Receipt acknowledged → Movement recorded → FAR updated, where applicable

The process does not necessarily require sophisticated software. For organisations with a manageable asset base, a properly controlled register with defined responsibility may work perfectly well. Where movements are frequent across many locations, a controlled workflow is preferable to spreadsheets maintained independently at each location.

The important point is ownership. Someone must be responsible for ensuring that an approved permanent movement ultimately reaches the FAR.

A second example: the machine was not missing

Consider a manufacturing company with two units.

During physical verification, a particular machine is not found at Unit A even though the FAR continues to show it there. The operations team informs the verifier that the machine was shifted to Unit B several months ago because production requirements changed.

At Unit B, the machine is physically available.

From an operational perspective, everyone may consider the matter resolved: the machine exists.

From a fixed asset control perspective, however, there is still a gap. When was it transferred? Who authorised the movement? Did Unit B acknowledge receipt? Was the transfer intended to be temporary or permanent? Why does the FAR still show Unit A?

The purpose of the movement register is not merely to prove that the machine exists. It is to maintain the trail that answers these questions.

What should Finance review periodically?

The register becomes more useful when it is reviewed rather than merely maintained. Depending on the volume of transactions, Finance or the responsible asset team can review it monthly or quarterly, particularly for:

• Permanent movements where FAR Updated is still marked “No”;
• Temporary movements outstanding for an unusually long period;
• Assets transferred without receiving acknowledgement;
• Movements without the required approval;
• Employee-to-employee transfers not updated in the asset master; and
• Cases where an asset tag or other identifier has changed.

This is one of the few areas where a relatively small periodic review can prevent a much larger reconciliation exercise later.

The control is simple; consistency is the difficult part

An Asset Movement Register is not a complicated document, and that is precisely why it is easy to underestimate.

When assets are stationary, maintaining their location is straightforward. The challenge begins when assets continuously move between employees, departments, branches and project locations while the FAR remains static.

A good movement process keeps the physical asset and its information trail connected.

The test is simple. Pick any transferred asset and ask:

Where did it come from? Where is it now? Who approved the movement? Who received it? And does the FAR reflect the current position?

If the organisation can answer those questions without searching through emails, messages and individual spreadsheets, its asset movement control is probably working.

If it cannot, the next physical verification may end up reporting differences that are not really asset shortages at all.

The asset moved.

The record simply did not move with it.

******

Disclaimer: This article is intended for general informational purposes and is based on practical observations relating to fixed asset verification and reconciliation. The appropriate controls and documentation may vary depending on the nature, size and internal processes of an organisation.