A printer is listed as Finance Printer in the accounting files but as Floor 2 Printer in the operational records. To connect the two records without guessing, use consistent asset identifiers, locations, and details of who is responsible. Include update rules that are easy to follow.
Data that helps you track assets
Distinguish asset names from identifiers
An asset name helps people recognize an item, but it may not be enough to distinguish one unit from another. Two printers of the same brand and model still need their own unique codes.
Keep the identification code separate from the asset name or description. The code links the same asset across different records, while the description explains the item’s type, brand, model, and distinguishing features.
The finance team will struggle to match records by code if the operations team only records the user’s name. For this reason, include the same code in maintenance records, transfer forms, and other supporting documents.
Record location and responsibility separately
The location shows where an asset is, while the responsibility field identifies whom to contact to confirm its use. Record these separately because an asset’s user does not necessarily work at their department’s location.
For example, the marketing department keeps its projector in a shared meeting room. Record the meeting room as the physical location, marketing as the managing department, and the designated staff member as the responsible person.
Build asset records with consistent identifiers
Establish unique codes and naming rules
When deciding how to record company assets, use one coding system for all recorded assets. You can use a simple format such as AST-000125, provided each code refers to only one asset and is not reused after that asset is disposed of.
Keep the unique code when an asset changes rooms, users, or departments. Avoid including locations or user names in the code because that information can change.
Use the manufacturer’s serial number as supporting data, rather than automatically making it the sole identifier. Some items do not have an easily readable serial number, so you still need to assign an internal code.
Agree on an order for asset names, such as type, brand, then model. This pattern helps the team avoid using different primary names, such as Admin Laptop and Office Notebook, for similar items.
Record location, status, and the responsible person
Prepare a master asset register to serve as a shared reference. Group information as shown below to make it easy to understand, but provide a separate field for each detail.
- Identification: unique code, asset name, category, brand, model, and serial number if available.
- Acquisition: acquisition date and cost as stated in the documents, along with the invoice or receipt document number.
- Location: branch or building, floor, and room or area.
- Responsibility: managing department and the responsible person’s identification details.
- Current state: usage status and physical condition.
- Update history: date of change, staff member, and supporting document references.
Use predefined lists for locations and statuses to avoid entries such as Head Office, HO, and Headquarters for the same place. Separate usage status, such as in use or in storage, from physical condition, such as good or damaged.
If the master register is also used for accounting reports, add fields according to company needs and policies. Recording an item in a tracking register does not automatically make it a fixed asset in the financial statements.
Example of a single asset record
For example, a printer with the code AST-000125 is named Brand A Model B Laser Printer and is located in the Jakarta Building, Floor 2, Finance Room. The printer is in use, is in good condition, and is the responsibility of Rina, whose employee number is recorded in a separate field.
Supporting documents may include receipt document BAST-018 and the related purchase invoice. When the printer moves to the administration room, continue using the code AST-000125. Update the location, the responsible person if this changes, and the change history.
Make data updates easier
Check the data before saving changes
Use the same quick check every time you update data, whether in a spreadsheet or an application. Before saving changes, make sure the following requirements are met.
- The asset code appears in the master register and is not used for another item.
- The destination matches the agreed location list.
- The new responsible person’s identity is clear and has been confirmed.
- Usage status has not been confused with physical condition.
- The effective date and evidence of the change have been included.
- The data before and after the change can be traced.
If information is incomplete, mark the request as awaiting confirmation and do not immediately replace the master data. This prevents the team from treating unconfirmed information as final data.
Establish a change and review workflow
The user or unit coordinator requests a change by providing the asset code, old information, new information, and supporting evidence. The asset administrator checks for completeness before updating the master register. A designated staff member then reviews the change within their authority.
Involve accounting staff in reviewing changes that affect financial records. A move between rooms does not always require the same review as a change in acquisition cost or an asset disposal.
Designate one master register as the reference and restrict who can edit it. Extract data for departmental needs from that register, rather than from separate lists updated without reconciliation to the master data.
Keep a history that includes the old data, new data, update time, staff member, and approval references. If you use a spreadsheet, keep the history on a separate sheet and restrict access to it.
Recording errors and how to resolve them
Duplicate codes or incomplete identification
If two rows use the same code, do not immediately delete one of them. Compare serial numbers, proof of purchase, receipt documents, and item details to determine whether the team has recorded one item twice or two different assets.
If one item has two codes, check the data before choosing which code to keep, and retain the old code as a reference. If two different items use one code, assign a new code to one of them and record the reason for the correction.
Location changes without data updates
Different locations in two files do not prove that an asset is missing. Check the update date of each record, confirm with the responsible person, then compare the information with transfer or receipt evidence.
Matching identifiers and evidence also helps you trace discrepancies when reviewing the data further. The article on asset register checks for tracing discrepancies discusses related steps without treating every mismatch as a physical loss.
Use records to inform your next decisions
Consistent records help the team identify items, locate them, know who is responsible for them, and check when their data changed. Linked codes, locations, statuses, and evidence make it easier for the team to update and trace data for both operational and reporting needs.
As a starting point, use one asset category to test the core format and change rules before expanding their use.
Learn more on the official Fisetra website.