Fixed Asset Register: the FRS 102 Guide

What a fixed asset register is — and why the law cares

A fixed asset register (FAR) is the controlled record of every fixed asset an organisation holds: what it is, where it is, what it cost, how it is being depreciated, and what it is worth in the books today. It is simultaneously an accounting record, a control document and the evidence base for tax claims and insurance. A good register answers four questions at any moment — what do we own, where is it, what is it worth, and can we prove it — and the gap between organisations that can answer those questions and those that cannot is almost always the gap between a register that is verified and one that has been rolled forward untouched for years.

In the UK the legal anchor is section 386 of the Companies Act 2006: every company must keep adequate accounting records, and those records must contain “a record of the assets and liabilities of the company”. Section 387 makes failure a criminal offence for every officer in default, and section 388 requires the records to be retained for three years (private companies) or six (public). ICAEW’s guidance for directors (TECH 01/11) treats a maintained asset register as the practical means of discharging that duty for fixed assets. The register is not, in other words, a finance nicety — it is how a statutory obligation is met.

The fields a compliant register needs

The template above carries the full field set. The principle: every field either feeds FRS 102 measurement, proves physical existence, or carries the tax trail. A register missing any of the three dimensions is incomplete — financial-only registers cannot evidence existence; physical-only registers cannot support the accounts.

Two fields do more work than the rest. The asset number is the unique, never-reused key that joins the physical tag on the asset to the accounting record in the ledger — reuse it, and a disposed asset’s history bleeds into a new one. The parent / component reference is what lets the register represent a single asset made of parts with different lives, which FRS 102 requires and most legacy registers cannot do. Get those two right and the rest of the structure follows.

FRS 102 Section 17 in brief

For UK GAAP reporters, FRS 102 Section 17 (Property, Plant and Equipment) governs how the register’s financial fields behave:

• Recognition and measurement (17.4–17.14). Assets are recognised at cost, including directly attributable costs of bringing them to working condition. Major components with materially different useful lives are depreciated separately — your register structure must support parent/component relationships.
• Cost model or revaluation model (17.15–17.15F). Entities may carry classes of assets at revalued amounts, provided revaluations are kept sufficiently up to date — which requires a repeatable valuation process.
• Depreciation (17.16–17.23). Depreciable amount (cost less residual value) is allocated on a systematic basis over useful life. Method, lives and residual values are reviewed when indicators of change exist.
• Impairment (Section 27). At each reporting date the entity assesses indicators of impairment — unverifiable or idle assets discovered during physical verification are classic triggers.
• Derecognition (17.27–17.30). An asset is removed from the register on disposal or when no future economic benefits are expected; the gain or loss — proceeds less carrying amount — goes to profit or loss. Disposals that are never processed are the ghost assets that distort everything downstream.
• Disclosures (17.31). For each class: gross carrying amount and accumulated depreciation reconciled from opening to closing balance — additions, disposals, revaluations, impairments, depreciation. Without a clean register this reconciliation is reverse-engineered every year-end; with one, it is a report.

Asset classes and the chart of accounts

Before any individual asset is recorded, the register needs a coherent asset-class structure — the set of categories every asset is filed under, mapped to the nominal ledger control accounts in the chart of accounts. Get the classes right and the register reconciles to the accounts, the FRS 102 disclosures fall out by class, and depreciation policy can be applied consistently. Get them wrong — too few classes, inconsistent definitions, or classes that do not tie to the ledger — and every downstream report has to be patched by hand.

• Classes should mirror how the accounts are presented: land and buildings, plant and machinery, fixtures and fittings, office and IT equipment, motor vehicles, and — from the 2026 changes — right-of-use assets, each tying to its own ledger control account.
• Each class carries a default depreciation policy (method, indicative useful life, residual-value approach) so new additions inherit a sensible treatment rather than being set ad hoc, while still allowing asset-specific overrides where needed.
• The class drives the capital allowances analysis too: a clean class structure makes it far easier to identify which assets are main-rate, special-rate or integral features for capital allowances — one structure serving both accounting and tax.

A register whose classes do not reconcile to the ledger is the most common reason a year-end fixed-asset reconciliation takes days instead of minutes. Fixing the class structure is usually the first structural step in any register rebuild, before a single physical asset is counted.

Component accounting in practice

Componentisation is the part of Section 17 that registers most often fail to support, and it matters more than its low profile suggests. Where an asset is made up of major parts with materially different useful lives, each part is treated as a separate component with its own cost, life and depreciation. A building might split into structure, roof, lifts, heating and electrical systems; a production line into the frame, the control system and the wear parts; a vessel or vehicle into the body and a major overhaul that is itself capitalised and depreciated over the period to the next overhaul.

• The register must be hierarchical. A flat one-line-per-asset register cannot represent a parent with components — which is why the parent/component reference is in the field set above, and why moving to a componentised model is often the trigger for a register rebuild.
• Replacement of a component. When a major component is replaced, the carrying amount of the old one is derecognised and the new one capitalised — a transaction a flat register simply cannot record cleanly.
• It feeds tax too. The same component breakdown that satisfies FRS 102 depreciation is what separates integral features and other qualifying plant out of a building for capital allowances — one structural decision, two compliance payoffs.

Depreciation: methods, lives and review

Depreciation is the systematic allocation of an asset’s depreciable amount over its useful life, and the register is where the policy is applied asset by asset.

• Method. Straight-line is the most common, but the method should reflect the pattern in which the asset’s benefits are consumed — reducing-balance or units-of-production may fit better for some plant. The register records the method per asset so the charge can be reproduced and audited.
• Useful life and residual value. Both are estimates, and both must be reviewed when there is an indicator that they have changed — heavier use, a shortened life, a different expected disposal value. Changes are accounted for prospectively, and the register has to hold the current estimates, not the originals.
• Consistency with the ledger. The depreciation the register calculates must be the depreciation posted to the accounts; a register whose depreciation has drifted from the ledger is a reconciliation problem waiting to surface at audit.

The revaluation model in practice

FRS 102 lets an entity choose, class by class, to carry property, plant and equipment at a revalued amount rather than at depreciated cost — but the choice comes with an ongoing obligation that the register has to support. Revaluations must be kept up to date so that the carrying amount does not differ materially from fair value at the reporting date, which means the model is not a one-off exercise but a recurring cycle.

• It applies to a whole class, not cherry-picked assets. If the revaluation model is adopted for a class (say, land and buildings), the entire class is revalued — the register must therefore identify class membership cleanly so the policy is applied completely.
• Revaluation surpluses and deficits have specific accounting. Increases generally go to a revaluation reserve through other comprehensive income; decreases below depreciated cost hit profit or loss. The register has to track the revalued amount, the revaluation reserve attributable to each asset and the depreciation on the revalued figure.
• It needs a repeatable valuation process. Keeping carrying amounts current requires periodic, defensible asset valuations — which is far more practical when the valuation attaches to a register that has been physically verified, so the values sit on assets that demonstrably exist.

Many entities adopt the revaluation model and then let the revaluations go stale, leaving carrying amounts that no longer reflect fair value — a finding auditors increasingly challenge. A register linked to a repeatable valuation cycle is what keeps the model compliant rather than aspirational.

Physical reconciliation: closing the existence gap

A register records what the organisation believes it owns. Physical reconciliation establishes what it actually owns, and the two are rarely the same after a few years of additions, moves and disposals that were never fully captured. Reconciliation classifies every line into one of three states:

• Found and matched — the asset exists, is in the expected place, and the record is correct. Confirm the verification date and move on.
• Ghost assets — on the register but not physically present: scrapped, stolen, transferred or never there. These overstate the balance sheet, inflate insurance premiums and corrupt capital allowances pools until they are written off with a documented schedule.
• Unrecorded additions — physically present but not on the register: assets bought and expensed in error, transferred in, or simply never capitalised. These understate the asset base and miss available relief.

A fixed asset verification that produces this three-way reconciliation, supported by durable asset tags, is what turns a register from a historical artefact back into a reliable record — and it is the evidence auditors increasingly expect for the existence and completeness assertions.

Keeping the register accurate: maintenance and controls

Most registers do not fail at a single point; they decay, one unrecorded movement at a time. Keeping one accurate is a matter of operational controls, not annual heroics:

• Additions control. A capitalisation policy and a procedure that ensures every qualifying purchase is tagged, numbered and recorded at the point it is brought into use — not discovered at year-end.
• Movement and transfer control. A named-owner process for recording when assets change location, site or custodian, so the register’s location data stays true between counts.
• Disposal control. A documented routine for derecognising assets that are scrapped, sold or retired — capturing the date and proceeds the accounts and the capital allowances computation both need.
• Rolling cycle counts. RFID or barcode cycle counts of high-value and mobile classes between full verifications, so accuracy is maintained continuously rather than rebuilt every five years.

Integration with ERP and finance systems

In most organisations the register does not stand alone — it lives in, or feeds, the finance system or ERP where additions are posted, depreciation is run and the nominal ledger is updated. The physical layer is captured in the field and reconciled back to the system record by the unique asset number.

• The asset number is the contract between the two worlds. The ledger record and the physical tag must share one unique, never-reused identifier; without it, field findings cannot be matched to accounting records reliably.
• The physical count is the source of truth for existence. Locations, custodians, conditions and verification dates flow from the field back into the ERP record, correcting data the finance system never sees on its own.
• Reconciliation is two-way. The ERP holds cost, depreciation and net book value; the verification holds existence and location; reconciling them surfaces both ghosts and unrecorded additions, and leaves both systems agreeing.

CPCON works to the system you already run rather than imposing a new one — capturing the physical data in the field and handing it back in the structure your ERP or fixed asset module ingests. Where a large share of the estate is IT equipment, our IT asset inventory service reconciles the same physical count to your CMDB and to the asset inventory your ISO 27001 auditor samples.

Spreadsheet or system? Choosing the right register platform

The free template at the top of this guide is a real, usable register for a small estate — but where the register lives should be a deliberate decision, not an accident of history. The right answer depends on scale and complexity, not on preference.

• A disciplined spreadsheet can serve a single-site organisation with a modest, stable asset base — provided it has unique, never-reused asset numbers, the full field set, and change control so it cannot be edited silently. It is far better than the common alternative, which is no register at all.
• A dedicated fixed asset system or ERP module becomes necessary as the estate grows: multiple sites, multiple users, component accounting, right-of-use lease assets, automated depreciation runs and a controlled audit trail are difficult to hold together in a spreadsheet without errors creeping in.
• The spreadsheet becomes the migration baseline. When the move to a system happens, a clean, verified spreadsheet — ideally one already reconciled to a physical count — is the ideal source to migrate from, rather than carrying forward a legacy system’s accumulated errors into the new one.

Whichever platform holds the register, the principle does not change: the data is only as good as the last time it was confirmed against the physical estate. A sophisticated system populated with unverified data is no more reliable than a neglected spreadsheet — the platform is the container, the verification is the substance.

The register and the audit

At audit, the register is tested against the standard financial statement assertions, and a recent physical reconciliation is the most efficient way to satisfy the two hardest ones.

• Existence — the recorded assets are real and can be located. Satisfied directly by a physical verification with tagged, traceable assets.
• Completeness — everything that should be capitalised is on the register. Satisfied by the unrecorded-additions findings of the same exercise.
• Accuracy & valuation — cost, depreciation and net book value are right and reconcile to the ledger by class.
• Rights & obligations — the entity owns or controls the assets, including right-of-use assets under the new lease rules.
• Presentation & disclosure — assets are correctly classified and the Section 17.31 reconciliation is produced cleanly.

Beyond the accounts: insurance, capital planning and decisions

The register earns its keep well beyond the financial statements. The same data that satisfies FRS 102 is what a dozen other decisions quietly rely on — and when the register is wrong, every one of them is wrong with it.

• Insurance and reinstatement. Declared values and sums insured are derived from the register. Ghost assets inflate premiums on equipment that no longer exists; unrecorded additions leave real assets uninsured. Underinsurance is typically only discovered at the worst possible moment — a claim — when an averaging clause cuts the payout. A register reconciled to a physical count, and to a reinstatement-cost valuation, is what keeps cover aligned to reality.
• Capital planning and replacement. Knowing the age, condition and remaining useful life of the estate — fields a good register carries — is the basis for forecasting replacement capital and avoiding both premature replacement and unplanned failure.
• Internal control and accountability. Custodian and location data make someone accountable for each asset, deter loss and theft, and make movements traceable — control that a financial-only register cannot provide.
• Mergers, disposals and grant compliance. Due diligence, carve-outs and grant-funded asset reporting all demand a register that can be relied on without a frantic clean-up first.

Because all of these uses draw on the same underlying data, the economics of getting the register right are compelling: one physical verification and reconciliation supports the accounts, the tax claim, the insurance position and the capital plan at once, rather than each function maintaining its own partial, conflicting view of what the organisation owns.

What changes on 1 January 2026 — the Periodic Review

The FRC’s Periodic Review 2024 amendments apply to accounting periods beginning on or after 1 January 2026 — so for December reporters they are live now. Two changes matter directly to asset registers:

• Leases on-balance-sheet (Section 20). Lessees recognise right-of-use assets and lease liabilities for most leases (short-term and low-value exemptions remain). Those right-of-use assets need asset numbers, classes, depreciation and tracking like any owned asset — registers and capitalisation policies must be extended to hold them.
• Transition data quality. Building the opening right-of-use balances, and proving the completeness of the lease population, is an asset-data exercise. Entities that combined it with a physical verification have found the same project also cleared years of accumulated ghost assets.

Building (or rebuilding) a register that stays accurate

1. Physical verification first. Count what actually exists — wall-to-wall verification — rather than copying forward the old register’s errors.
2. Tag everything. Durable asset tags make every future count scan-based and cheap.
3. Reconcile and clean. Match physical findings to the ledger; write off ghosts with a documented schedule; capitalise unrecorded additions; correct classifications and componentise where Section 17 requires it.
4. Operationalise. Movement, disposal and transfer procedures with named owners — plus rolling RFID or barcode cycle counts so accuracy is maintained, not rebuilt every five years.

The register also drives tax: capital allowances claims (AIA, full expensing, writing down allowances) are made at asset level, and HMRC enquiries are answered with exactly the records this guide describes. Where the value sits in brands, technology or customer relationships rather than plant, our intangible asset valuation practice covers the off-register assets, and our asset valuation service supports the revaluation model and fair value work the register feeds.

CPCON verifies, tags and reconciles fixed asset registers for organisations across the UK, drawing on 30+ years and 4,500+ projects reconciling the physical, the logical and the accounting view of what an organisation owns — so the register your auditor samples, your tax adviser relies on and your insurer prices is the same register, built on data that has actually been confirmed.