What are the features of a better fixed asset management software?
There are three common features to good fixed asset management: an inventory can make it easier to record data over and over, every state of assets from purchase to end-of-life is found in the system, and the financial system is accounted for. The functional details that are being developed around these three points are shown below by scene.
Start with a real experience.
And the doubt of life: how much did the mobile sweep save?
In 2023, we took on a fixed asset count for a restaurant chain. The books showed over 200 locations and more than 8,000 pieces of equipment. The finance team's asset register differed from actual warehouse stock by nearly 15%. Oven counts didn't match, and several freezers were listed at a restaurant that had already closed.
They used Excel to add paper: the inventoryer took the printed form to the scene, checked the device number, went back and recorded the results into the system. The full-quantity count came down at a time, six of the counted officers, nearly three weeks later, and then it took another week or two to process the error.
We switched to mobile scanning. Each piece of equipment got a QR asset tag. Staff scan it with a phone or PDA, and the system automatically identifies the asset number and shows its name and current location. They tap 'In stock' to confirm a match or flag it 'Verify' and upload a photo from the site.
The second round of inventory, two of the inventory officers, completed full scans in five days, and the error rate dropped to less than 2% from a dozen percentage points in the previous round.
So the first of the selected types, to see if the inventory function supports a moving end sweep, whether it can be delineated (the warehouse, where the signals are not good in the garage), or whether it can be modified directly during the scan. With an PC-end inventory interface, there is basically no on-site.
The count requires a few details.
- (a) Inventory approach: by department, by location of deposit or by asset class? Does not support a customised inventory task?
- Discrepancies: can a single negative or positive margin be generated directly in the system?
- RFID Extension: Large assets and high value (e.g. metal brands for electrical equipment), can the RFID bulk count be expanded at a later stage?
Assets are not just "in or out." They're all in the life cycle.
Many people think that fixed asset management is "do a desk, count it at the end of the year" and it really turns out that there's more to the problem with assets. One equipment from the time it was purchased into the library has to go through access, transfer, repair, depreciation, depreciation, write-off, every step must be recorded.
Take asset transfers. One warehouse automation factory has more than 30 teams, and forklifts and AGVs are often borrowed temporarily by different workshops. Transfers were tracked in Excel, and team leaders passed on who borrowed the equipment, when it was due back, and what wear or losses occurred by word of mouth. At month-end, asset managers had to visit three or four workshops to reconcile the records.
They then went online with a system that managed to move, and put two dimensional codes on each forklift, and who would have to use it to start the transfer order, indicate why and what time they were expected to return, and check it again when they returned. The asset was in whose hands, when it was transferred, and where it was in which workshop -- the system -- was clearly visible.
This involves several key points of the life cycle:
- Repository: Can the purchase order automatically remove the supplier, original value, expected useful life when it is transferred to a fixed asset card?
- Depreciation: Are multiple depreciation methods (line, double-deduction, sum of years) supported and can they be automatically charged on a monthly basis?
- Maintenance: Could the maintenance worksheet be linked to record the cause of each failure, maintenance costs and number of days of shutdown?
- End of life: Is the process of end of life compliant and residual income automatically accounted for?
When Shanghai-based technology works with manufacturing-like enterprises, it usually links maintenance records and depreciation data -- a device that has accumulated maintenance costs above 60 per cent of its original value, and the system automatically suggests "recommended end of life" -- much more reliable than simply empirical judgement.
Can we hold on to a multi-organizational location?
Once asset counts reach a certain point, the organizational structure gets more complex. One retail group has more than 30 regional companies and more than 400 stores. Each store has its own asset administrator, and a shared finance center reconciles the accounts centrally.
The selection depends on whether the system supports multi-organism -- is there a separation of data from different stores, can headquarters aggregate across the organization, can it be detailed to "only look at the assets of one's own store" -- if the system has a single organizational structure, that size will barely hold.
And the level of storage is flexible. For example, a group that runs a chained hotel, which may be located on the sixth floor of the "group-region-city-hotel-store-room" system, whether or not it can define the level, determines whether future assignments and inventories can be located in specific locations.
And the financial system is a reconciliation.
Many companies have fixed asset management software, which was originally driven by the finance department — when monthly reconciliations are made, the asset manager export a desk account to finance, and the financial re-checking with the general ledger module, and finds that discrepancies need to be re-examined.
A really good system should be able to:
- (a) Automatically generate accounting documents for the introduction of an ERP or financial system when new, changed or scrapped asset cards;
- (a) Automatic monthly depreciation drawings and the generation of corresponding evidence of depreciation;
- The asset desk and master record data are reconciled on a monthly basis, with the discrepancies automatically marked.
The interface is confirmed in advance: provides a standard API interface (recommended), supports the import export of files, or must customize development? We have met with a client before, and the selected system does not support and connects with friend U8, and it takes hundreds of thousands of times to do it twice, and the value for money is very poor.
You can check the list when you choose.
A short list of the dimensions mentioned above has been compiled and can be used directly in communicating with the manufacturer:
- (a) Stock count: Does the mobile end-of-way sweeps drive are supported? Can you work offline? Can you generate a discrepancy sheet online with the negative-end gain?
- Tagging: Is bulk printing available for QR code labels, barcode labels, and RFID tags?
- Depreciation: What methods of depreciation are supported? Can they be automatically charged on a monthly basis?
- Redeployment: Does the transfer process require approval? Can it be recorded?
- Maintenance: can maintenance bills be linked, maintenance costs and shutdown time recorded?
- End of life: Is the process of end of life compliant? Can residual values be automatically recorded?
- Organization: Does it support a multi-organizational structure? Can the authority be detailed to specific people?
- Place of deposit: Is the level of storage self-defined?
- Interface: Are APIs available? Can they be connected to existing ERP/Fificiary systems?
- Statement: Is a self-defined statement possible? Does it support the full life cycle analysis of assets?
- Deployment: SaaS or local; where is the data storage location?
- Implementation cycle: How long does the standard normally operate? Does it include training?
- Cost structure: is there an annual fee based on the number of assets or a user fee based on the number of users?
These 13 questions are basically a judgement of the manufacturer's lack of credibility. If the other party is not clear or vague, it is suggested that the other person should move to another one.
Two of the easiest pits to step on before landing.
Two last reminders are repeated in our projects.
It is important that the rules on asset codes be harmonized well in advance.When you saw the company's online system, the number of the same device was in the financial account "FD-2021-0038", in the administrative desk, "office equipment 038," and in the warehouse, another number, which took two months to clean up. Before that line, you set the code, and the whole company uses one.
One or two scenes before the full-scale spread.It is recommended that a department or a doorshop be selected for piloting, running the whole point - transfer - to scrap three core processes and then extending them to the company as a whole. A one-time full-scale spread would have high costs of adjusting in case of problems.
The matter of fixed asset management, which appears to be a back-office exercise, is actually related to procurement, administration, finance and operations — the selection of the pairing tool is only the beginning, clear rules are set, the process is smooth, and the book and physical alignment is real.

Ms. Lei
Mr. Pang