Many new audit teams feel the weight of fixed asset audits when the asset register, financial statements, and evidence trail do not tell the same story. The context from pajak.go.id’s discussion on financial statement integration shows an increasingly real operational pressure: financial data needs to be ready for various purposes. If asset discrepancies still depend on the memory of the person in charge or manual document searches, the review can easily expand and become difficult to justify.
An asset discrepancy is not just a difference in numbers on a spreadsheet. In practice, discrepancies can arise because an asset cannot be found, its location changes without an update, its usage status is unclear, acquisition documents are scattered, or asset disposal has not been fully recorded.
Closing discrepancies aims to produce decisions that can be traced. It is not only about making the numbers match again, but also ensuring that the reasons, evidence, authorization, and record changes are stored properly.
Step 1: Define the discrepancy and scope
Start by defining what is considered a discrepancy. A useful simple definition is the difference between asset records and verifiable conditions, whether in terms of existence, value, location, status, or person responsible.
After that, determine the review period. For example, the audit may only cover assets active as of 31 December, or all assets that have undergone movements since the beginning of the current year.
Data that must be aligned
The audit team should align at least five elements before going too far into the physical inspection:
- Asset number or code.
- Asset name and description.
- Last recorded location.
- Asset status, such as active, damaged, loaned out, or in the disposal process.
- Person responsible or asset-owning unit.
If these five elements are not yet aligned, the discrepancy that appears may come from an administrative issue, not from a missing asset. For example, a printer recorded at the head office may actually have been moved to a branch, but the transfer form has not yet reached the accounting department.
Discrepancy limits used
Also determine the asset groups to be reviewed. High-value assets, assets that are easy to move, and assets frequently borrowed between departments usually need to be prioritized.
Discrepancy limits do not always have to be in monetary value. For an operational audit, one missing laptop can be more important than several chairs in the wrong location, because the risks related to data access and usage responsibility are different.
Step 2: Review data sources and the evidence trail
Once the scope is clear, shift the focus to the quality of evidence. A single asset record is rarely enough to close a discrepancy, especially if the asset has a long history or has moved between units.
A good evidence trail helps auditors answer three things: the asset once existed, the asset moved on a clear basis, and its latest status can be proven. Without that evidence, the team is only replacing one assumption with another.
Main records to reconcile
Use the fixed asset register as the starting point, then match it with supporting documents. Documents that are often relevant include handover minutes, purchase invoices, transfer records, repair documents, loan forms, and disposal approvals.
Pay attention to the asset history, not just its latest position. If an asset moved from the operations department to the warehouse, then to a project site, each movement needs to have a date, the party handing it over, the party receiving it, and the reason for the transfer.
The strongest evidence
Physical evidence is usually strong when it contains an asset identity that can be matched directly with the records. Photos of assets with readable codes, label scan results, and confirmation from the person responsible can strengthen the conclusion.
However, physical evidence still needs context. A photo without a date, location, or examiner identity is weaker than an inspection record showing who checked what, where, and when.
If the organization uses labels to trace assets, choose an identification format that suits field conditions, not merely one that follows old habits. The discussion on choosing barcode or QR code for asset tracking can help when physical evidence needs to be made easier to read and more consistent.
Step 3: Set rules for closing discrepancies
Closing discrepancies requires decision rules that are agreed upon before cases are discussed one by one. Without rules, similar cases can be treated differently because of time pressure or the position of the asset owner.
These rules do not need to be complicated. What matters is that all parties understand when a discrepancy may be closed, when reclassification is needed, and when it must be escalated to a higher authorization level.
Closure criteria
A discrepancy can be considered for closure if the evidence is sufficient to explain the cause. For example, if an asset is found in a different location and there is evidence of a transfer that was recorded late, the appropriate action may be to update the location, not to write off the asset.
Use concise criteria such as the following:
- Physical evidence is available and matches the asset identity.
- The movement history can be explained.
- The asset status is supported by documents or confirmation from the relevant party.
- The value or impact of the discrepancy is within the approved tolerance limit.
- Authorization to change the records has been given by the authorized party.
Tolerance limits should be set according to internal policy and the asset’s risk level. For assets that affect safety, data, or core operations, an administrative tolerance that is too loose can become a problem.
When it needs to be reviewed again
A discrepancy needs to be escalated if the evidence contradicts itself, the asset is material in value, or the last person responsible cannot confirm the asset’s position. Escalation is also appropriate when a pattern of recurring discrepancies appears in the same location or unit.
For example, if three work devices from one department always move without a handover form, the problem may not lie with a single asset, but with process discipline. In cases like this, closing the discrepancy without fixing the workflow will only postpone the next problem.
Step 4: Test improvements before use
Before applying changes to the entire asset register, test them first on a small sample. This approach helps the team see whether the new rules truly clarify the data or instead add unnecessary administrative work.
Choose samples that represent different types of problems. For example, five assets in the wrong location, five assets without a clear person responsible, and five assets whose status is inconsistent between accounting records and department records.
Test on a small sample
For each sample, run the flow from beginning to end: review the records, find evidence, determine the decision, request authorization, then update the data. Record the time needed and the points that most often cause delays.
Input errors often appear at this stage. Similar location names, mistyped asset codes, or carelessly selected statuses can create new discrepancies after old ones have been closed.
Signs that the data is stable
Data starts to become stable when a change in one source is reflected consistently in other sources. If the asset register shows that an asset has been moved, department records and handover evidence should support the same information.
Also pay attention to time synchronization. If a location update is only entered two weeks after the asset is moved, auditors need to know whether that delay is still in line with procedure or has become a source of risk.
Step 5: Establish routines and an audit trail
Discrepancies that have been closed can still reappear if recording routines are not improved. Therefore, the final stage is to build work habits that keep data ready for review.
An audit trail, or traceable record of changes, needs to show what was changed, who changed it, when the change was made, and the reason for the change. Without an audit trail, data updates can look like one-sided corrections.
Regular review rhythm
Create a realistic periodic review rhythm. For assets that move frequently, monthly checks may make more sense than waiting for the annual audit.
For relatively fixed assets, quarterly or semiannual reviews may be sufficient, depending on internal policy and usage risk. What matters is that the schedule is known by accounting, asset owners, and the unit responsible for recordkeeping.
Mandatory change records
Every important change needs to leave a record. Changes in location, changes in person responsible, status changes, code corrections, and discrepancy closures should not be made without a documented reason.
The record format does not have to be long. A single line containing the date, asset, change, evidence basis, person making the change, and approver is often enough to make decisions easier to justify.
With these five steps, the audit no longer stops at the question of “whether the asset exists or not.” The team can explain why the discrepancy appeared, what evidence supports the decision, and what improvements prevent similar cases from recurring.
Start with one asset group that most often creates discrepancies.
Learn more on the official Fisetra website.