Asset reconciliation is the process of comparing physical assets against the asset register and accounting records, then resolving any differences found.
Asset reconciliation is the process of comparing what physically exists against what the asset register and the accounting records say exists, then resolving the differences. It is the follow-through step: counting and asset verification surface the discrepancies, reconciliation explains them and corrects the records, and a fixed asset audit later checks that all of this actually happened.
How reconciliation works
A reconciliation needs three inputs: the results of a physical count or verification, the asset register, and finance’s fixed asset ledger. The work is matching them line by line and sorting every difference into one of a few buckets - on the floor but not in the records, in the records but not on the floor, in both but with conflicting details (wrong location, wrong owner, wrong value).
The matching is only as good as the identifiers. Where every item carries a tagged ID recorded in both the register and the ledger, lines match mechanically; where finance has “12 x tablet” as one ledger line and the register itemises each device, someone has to build the mapping first, and that mapping is worth keeping for next time.
Common causes of mismatches
- Unrecorded disposals - equipment scrapped, sold, or recycled without anyone updating the records, leaving ghost assets that still sit on the books and accrue depreciation.
- Unlogged movements - transfers between people, departments, or sites that happened by handshake, so the register’s location and owner fields describe last year.
- Purchases that bypassed the process - items bought on a card or expensed, physically present but never registered.
- Double records - the same item entered twice after an import, or itemised in one system and grouped in the other.
- Loss and theft - the difference nobody recorded because nobody knew.
Resolving differences cleanly
The rule: investigate first, adjust second, document always. A missing item is a question, not a deletion - check the audit history for the last recorded event, ask the last known holder, check whether a disposal was done but not logged. Only once the cause is known should the records change, and every adjustment should carry a reason and an approver. Write-offs and ledger corrections belong with finance, not with the person who maintains the register - keeping the counter, the record-keeper, and the approver separate is basic segregation of duties, because the ability to both lose an asset and erase it from the records is precisely the gap a fraudster needs.
The pattern of differences matters as much as the fixes. One missing cable is noise; a steady leak of unrecorded disposals from one site is a process failure worth fixing at the source.
Reconciliation in practice
Reconciliation done annually is archaeology; done quarterly it is housekeeping. The teams that find it painless keep one register as the operational source of truth, export it for finance at period end, and rely on per-asset history to trace when each mismatch was introduced. AMPthilly supports this loop with CSV export of the register and an audit history on every asset, so a discrepancy can be traced back to the last recorded checkout, transfer, or edit rather than argued from memory.
Related terms
- Asset Verification - physically confirming the assets that reconciliation compares
- Fixed Asset Audit - the independent review of assets, values, and records
- Audit Readiness - staying reconciled so audits hold no surprises
- Internal Controls - the process checks that stop mismatches recurring
- Segregation of Duties - keeping counting, record-keeping, and approval in separate hands