The Regional Finance Agency of Kepahiang Regency explains that DIPAYANG (Digitalisasi Pengamanan Aset Kepahiang) automatically processes asset additions or reductions once a transaction has Final status in the reconciliation of regional government-owned assets (BMD). This practice is not a standard for all organizations, but it highlights the importance of deciding how to resolve data discrepancies before updating the asset register.
At period-end closing, a list of findings may look complete even though the team has not made final decisions. Fixed asset reconciliation needs to connect records, evidence, and decisions so the team can trace how each discrepancy was resolved.
Why reconciliation is not complete when discrepancies are found
Field findings show conditions at the time of inspection, but do not directly determine changes to the register. A machine that cannot be located, for example, may be undergoing repairs, may have been moved, or may still need to be traced.
Authorized personnel need to review the evidence before determining the asset’s status. The team must therefore not immediately use a “not found” note as grounds for writing off an asset.
Separate inspection findings from final decisions
Provide separate columns for findings, follow-up status, and the final decision. This allows the team to retain the initial information even if the final conclusion changes.
For example, the initial finding might read “serial number differs”, the follow-up status “awaiting replacement documentation”, and the final decision “identification details updated based on replacement evidence”. If the team overwrites the initial finding with the final decision, the reason for the change is no longer clear.
Without this separation, the same discrepancy may reappear in the next period because its resolution status is unclear. Auditors will also have to reconstruct the sequence of events from scattered conversations and files.
Practical steps to align records and decisions
Start with baseline data and discrepancy types
Save a copy of the register as of the reconciliation cutoff date, then assign a unique case number to each discrepancy. Use that number to link the asset, findings, supporting documents, approvals, and changes made.
Group discrepancies by type, such as differences in identification details, location, value, duplicate records, or usage status. This grouping helps the team assign the appropriate reviewer without assuming that all discrepancies have the same cause.
Define the status, responsible person, and basis for the decision
Use simple workflow statuses, such as Open, Under Review, Awaiting Approval, and Closed. Use Closed only after an authorized person has approved an evidence-based decision and the team has implemented any necessary changes.
- Assign one person responsible for following up on each case.
- Specify the required documents and their submission deadlines.
- Record the proposed decision and its rationale.
- Determine the approver based on the type and impact of the change.
- Record the reference for the register update or the reason for making no change.
Align the approval workflow with organizational policies and applicable authority levels. A location correction may only require review by the asset controller, while a change in value or derecognition may require a financial assessment and approval from other parties.
Example: a machine is found, but the records do not match
A machine identified as M-042 is recorded as being in production room A, but staff find it in production room B during an inspection. The person responsible for the case obtains the transfer record and confirmation from the recipient, then submits a request to correct the location.
The change history includes the field contents before correction, “production room A”, and after correction, “production room B”. It also includes the case number, effective transfer date, update time, person making the change, approver, and document references.
Because this case concerns location only, the team does not change the acquisition cost or accumulated depreciation without another verified reason. The asset controller closes the case after confirming that the correction has been recorded in the register.
How to implement this without adding complexity
You do not need to prepare a lengthy report for every minor difference. You can use a single tracking list as long as each case has a consistent reference number and evidence that is easy to find.
Check completeness before closing a case
- Ensure the asset’s baseline data matches the item’s identification details and case number.
- Review acquisition cost, accumulated depreciation, and book value if affected.
- Link supporting documents directly to the relevant case.
- Include the rationale and approval in the final decision.
- Retain data from before and after the change, including who made it and when.
- Align the follow-up status with the results of the update verification.
If a correction affects accounting figures, reconcile the register with the general ledger and related journal entries. Updating the asset list alone is not enough if the team has not reconciled the affected balances.
Distinguish the transaction’s effective date from the date the correction is recorded so that the timing of the business event is not confused with the timing of its administration. For periods that have already been closed, the team should review the treatment of corrections in accordance with the organization’s accounting policies and authority levels.
Keep evidence easy to trace
Use file names that include the case number and document type, rather than just the asset name. If the team keeps evidence in shared storage, ensure that reviewers can access it and that links continue to work after the case is closed.
If the system does not automatically retain a change history, archive the versions before and after the update along with a change log, with restricted access. Do not rely on a single working file that is continually overwritten as the only record of resolution.
Mistakes that leave discrepancies unresolved
Temporary statuses often remain unchanged because the team has not set a deadline or identified who must make the next decision. Supplement an “awaiting confirmation” label with the name of the party being asked to confirm, the document being awaited, and the next review date.
Evidence that is stored but not linked to a case also makes resolution more difficult. A photo of a machine without a case number or readable identification details may not be sufficient to show which asset record it supports.
The team needs to verify both the asset’s existence and the basis for recording it; this principle is also relevant when assessing the risk of assets recorded without supporting evidence. However, incomplete evidence is a reason to continue the review, not automatic grounds for concluding that an asset does not exist.
If the team has not obtained an answer as period-end closing approaches, keep the case marked as unresolved and explain why. The finance team can review its reporting implications separately, without forcing a Closed status simply to make the list look complete.
Benefits for financial decisions and audits
A well-maintained register does not mean that every case is always resolved without exception. What matters is that the team can explain the circumstances of each case: its findings, responsible person, decision, and changed records.
Fixed asset reconciliation is complete after the team has documented the decision and verified its implementation, not merely matched the data. A complete audit trail helps reviewers understand the reasons for changes without relying on the memory of the person who made them, although it does not guarantee any particular audit outcome.
The next review can begin with the longest-outstanding cases that still lack a complete basis for a decision.
Learn more on the official Fisetra website.