What Is Asset Reconciliation?

Asset reconciliation is the process of comparing what physically exists against what the asset register and the accounting records say exists, then investigating and 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.

The word covers two jobs that pull in different directions. Operations and IT care about the physical floor against the asset register - does each item exist, and is it where the record says it is. Finance and audit care about the fixed asset register against the general ledger - do the values agree, including cost, accumulated depreciation, and net book value. A good reconciliation bridges both rather than leaning on one.

What you will learn

• The three views you reconcile
• How to reconcile fixed assets, step by step
• A worked asset reconciliation example
• Reconciliation cadence: how often and what
• Reconciliation vs verification vs audit
• Metrics that show reconciliation is working
• Common causes of mismatches
• Resolving differences cleanly
• Reconciliation in practice
• FAQ

The three views you reconcile (two-way vs three-way)

Every reconciliation draws on up to three sources of truth, and naming them is the single most useful framing in the discipline:

• The physical floor - the assets actually present, found by a count or verification walk.
• The operational asset register - the working record operations or IT maintains: owner, location, status, condition, serial number.
• The fixed asset ledger - finance’s fixed asset subledger and the matching general ledger (GL) control account, carrying cost, accumulated depreciation, and net book value.

Between these you run two distinct tie-outs. Register-to-floor answers questions of existence and location: is the item real, and is it where the register claims? Register-to-ledger answers questions of value: does the cost, accumulated depreciation, and net book value in the fixed asset register (FAR) agree with the GL control account? Doing only one of these leaves a blind spot - you can have every laptop physically accounted for while the ledger still carries thousands in depreciation on machines that were scrapped years ago.

Reconciling the floor, the register, and the ledger together is three-way reconciliation. It is the model nearly every mature programme uses, because each pair catches errors the others cannot: the floor exposes ghost assets and untracked items, the register exposes stale ownership, and the ledger exposes capitalisation and disposal errors that never reach the floor at all.

How to reconcile fixed assets: step by step

A repeatable fixed asset reconciliation runs in a set order. Doing the value tie-out before the physical work matters - it stops you chasing a floor discrepancy that is really a ledger entry error.

1. Gather the records. Pull the asset register, the GL control account balance and fixed asset subledger, depreciation schedules, purchase invoices for the period’s additions, and disposal receipts. Fix a single “as at” date so every source describes the same moment.
2. Tie the GL to the register first. Reconcile the fixed asset register to the general ledger before anyone walks the floor: opening balance, plus additions, less disposals, less depreciation, equals closing net book value. Resolve the paperwork-only differences here.
3. Run the physical count. Verify each item exists and capture its location, owner, and condition. Tagged IDs make this match mechanical; see asset tags for why a scannable identifier on every item removes most of the guesswork.
4. Check depreciation and accumulated depreciation. Confirm each asset is depreciating over the right useful life and that accumulated depreciation and net book value in the subledger reconcile to the ledger.
5. Classify every difference. Sort each into a bucket: on the floor but not recorded, recorded but not found, or present in both with conflicting details (location, owner, or value).
6. Investigate root cause. Trace each difference through the audit history before changing anything - a missing item is a question, not a deletion.
7. Post adjustments and publish the result. Make approved corrections, route write-offs and ledger entries to finance, and issue a tie-out summary plus an exception list so the next cycle starts from a known position.

A worked asset reconciliation example

A short illustration makes the mechanics concrete.

A site register lists five laptops. The physical count finds four. That single line difference could mean theft, a disposal, or a move - and the resolution path is different for each, so you investigate before you adjust.

You open the audit history for the missing serial number. The last recorded event is a checkout to an employee who moved offices three months ago. There is no disposal record and no condition note suggesting loss. The most likely explanation is an unlogged transfer: the laptop physically moved sites but its location field was never updated.

The fix is to update the location, not write the asset off, with a reason (“relocated to Office B, confirmed with holder”) and an approver recorded against the change. Nothing flows to the ledger because the asset still exists and its net book value is unchanged - only an operational field was stale.

Had the history instead shown the device was returned and sent for recycling with no posting, the path would reverse: you would retire the asset, and finance would remove its remaining net book value and stop accruing depreciation, clearing a ghost asset off the books. Same symptom on the floor, two very different corrections - which is exactly why the investigate-first rule exists.

Reconciliation cadence: how often and what to reconcile when

There is no single frequency, because the two tie-outs move at different speeds. A simple cadence guide:

• Monthly / each period close - GL-to-register tie-out. Tie the fixed asset register to the general ledger control account every period end so the books are corrected before they close. This is paperwork, not a floor walk, and it keeps period-end reconciliation cheap.
• Annually at year-end - full physical count. Run a complete physical count and three-way reconciliation at least once a year, aligned with the financial year-end, so any write-offs land in the right period.
• Quarterly or rolling - high-churn, high-value categories. Risk-adjust by mobility and value: IT equipment, tools, and vehicles move and disappear faster than fixed plant, so reconcile them more often.

On top of this calendar-driven rhythm, run event-driven reconciliation when something disrupts the estate: after a large purchase batch, an office move, or an offboarding wave. Reconciling close to the event is the difference between explaining a discrepancy from last week’s records and arguing it from memory a year later.

Reconciliation vs verification vs audit

These three terms are routinely blurred, but they are distinct steps in a chain:

• Verification is physically confirming that an item exists, where it is, and what condition it is in. It produces the floor data.
• Reconciliation compares the three views - floor, register, ledger - and corrects whichever record is wrong. It produces a clean, agreed set of records.
• Fixed asset audit is an independent check, usually by someone outside the process, that the reconciliation was done and the records can be trusted.

In short: verification gathers the evidence, reconciliation resolves it, and the audit confirms it. The same separation underpins good internal controls - the people doing each step should not all be the same person.

Metrics that show reconciliation is working

Reconciliation is an ongoing control, not a year-end clean-up, and a few lightweight metrics make that visible:

• Exception / discrepancy rate - reconciling items as a share of total register lines. A falling rate over successive cycles is the headline signal.
• Match rate - percentage of register lines that tie out cleanly to both floor and ledger on the first pass.
• Location-mismatch rate - lines where the item exists but is not where the register says, a proxy for unlogged movements.
• Duplicate count - the same asset recorded twice, usually an import artefact.
• Average time to resolve an exception - how long an open difference sits before it is explained and corrected.
• Recurring categories by site - which sites and asset types keep generating the same discrepancy, pointing you at the process to fix rather than the line to patch.

Tracked cycle over cycle, these turn reconciliation from a periodic scramble into a trend you can manage.

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 or capitalised.
• Capitalisation errors - purchases booked to the GL but never added to the fixed asset register, so the control account and the subledger drift apart.
• 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: every asset carries a full audit history of checkouts, transfers, ownership and status changes, and field edits, so a discrepancy can be traced back to the last recorded event rather than argued from memory. The register holds purchase price and date, supplier, warranty, expected useful life, and depreciation context, and exports to CSV for the finance tie-out - giving operations and finance the same line items to reconcile against.

Tools that make this easier

AMPthilly keeps one register for IT and physical assets, with QR labels you scan from a normal phone browser to open an asset and check its history on the spot - no app install. The free plan covers 3 users and 25 assets with full audit history, so you can test the reconciliation loop before committing. Start free - no card required.

FAQ

What is the difference between asset reconciliation and asset verification?

Verification is the act of physically confirming an item exists and noting its condition and location. Reconciliation is the broader process of comparing the three views of your estate - the physical floor, the asset register, and the fixed asset ledger - and correcting whichever record is wrong. Verification feeds reconciliation: you cannot reconcile the floor against the register until you have first verified what is actually on the floor. A fixed asset audit then independently checks that the reconciliation was done properly.

What is three-way asset reconciliation?

Three-way reconciliation ties together all three sources of truth at once: the physical assets found by counting, the operational asset register, and finance’s fixed asset subledger or general ledger control account. The register-to-floor tie-out confirms existence and location; the register-to-ledger tie-out confirms values - cost, accumulated depreciation, and net book value. Doing only one pair leaves a blind spot, so mature programmes reconcile all three.

How do you reconcile the fixed asset register to the general ledger?

Pull the general ledger control account balance for fixed assets and the total of the fixed asset register (or subledger) for the same date, then explain every difference between them. Walk through additions (capitalised purchases that should appear in both), disposals (items removed from one but not the other), depreciation and accumulated depreciation, and any reclassifications. The goal is that register cost less accumulated depreciation equals the net book value carried in the GL, with a documented reason for each reconciling item.

What is a fixed asset reconciliation example?

A site register lists five laptops; a physical count finds four. You trace the audit history and find the fifth was transferred to another office but never re-logged. The fix is to update the location rather than write it off, with a reason and an approver recorded. Had the history shown a disposal that was never posted, you would instead retire the asset and let finance remove its remaining net book value from the ledger.

Who is responsible for fixed asset reconciliation?

It is a shared control. Operations or IT owns the physical count and the asset register - existence, location, and condition. Finance owns the fixed asset ledger - cost, depreciation, disposals, and the GL control account - and posts the value adjustments. Internal audit independently confirms it happened. Keeping the counter, the record-keeper, and the approver as separate people is deliberate segregation of duties.

How often should assets be reconciled?

Tie the general ledger to the register monthly or at each period close, and run a full physical count and reconciliation at least annually at year-end. Estates with a lot of movement - equipment changing hands, frequent purchases and disposals - benefit from quarterly or rolling checks of high-churn, high-value categories like IT equipment, tools, and vehicles, because differences are far easier to explain when the events are weeks old rather than a year old.

What records do you reconcile assets against?

Usually three views of the same estate: the physical items found by counting or verification, the asset register operations maintains, and the fixed asset ledger finance maintains. Register-to-floor differences reveal operational problems like unlogged transfers or unrecorded disposals; register-to-ledger differences reveal accounting problems like purchases capitalised but never registered, or items recorded at different values in each system.

The takeaway

Asset reconciliation is the bridge between three views of the same estate - the physical floor, the asset register, and the general ledger - and the discipline of investigating, correcting, and documenting every difference between them. Run the GL tie-out at each period close, the full physical count at least yearly, and risk-based checks on whatever moves fastest, and reconciliation stops being a year-end scramble and becomes a quiet, continuous control.

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