Fixed asset terms, defined.

A tax deduction a company can generally take when it permanently discards business property instead of selling it. The IRS treats an abandonment loss on business property as generally deductible, and ordinarily as an ordinary loss where the disposal is not a sale or exchange. It only reaches the return if the disposal reaches the records. Unless the company has made a general asset account election, a piece of equipment that was discarded but never recorded as retired can leave this deduction unclaimed while the asset keeps depreciating for tax. Whether a loss applies to a specific asset is a question for the company's tax team.

See also: Retired asset · General asset account (GAA) election · Composite depreciation · Retired on the Floor Isn't Retired for Tax

A battery-powered RFID tag that pings its position continuously, producing real-time location rather than a point-in-time read. Also called real-time location system (RTLS) tracking. Active tags typically cost well over 10 times a passive tag, sometimes 100 times more for premium tags, and require a facility-wide network of readers and antennas sized to the building and the accuracy needed. That continuous signal matters for some operational use cases, such as tracking a forklift moving through a facility in real time. It answers the same existence and location question as passive RFID, only faster. It does not extend RFID's reach into detecting untagged assets or assessing condition.

See also: Passive RFID · RFID · The Fixed Asset Gap RFID Alone Can't Close

The uncoordinated proliferation of independent AI agents and automated workflows across an enterprise, each producing outputs that no shared layer reconciles or governs. As organizations add AI agents to inspection, monitoring, and document-processing tasks, each agent operates as its own island, producing output that no other system checks against. Some estimates put the resulting ROI erosion at up to 50 percent, as duplicated computation, conflicting outputs, and unreviewed exceptions consume the value the automation was supposed to create. Agent sprawl is a governance problem, not a technology problem. It compounds with every new AI deployment unless an orchestration layer coordinates what the agents produce.

See also: Universal Orchestration · Automation Plays an Instrument. Orchestration Conducts the Orchestra.

A software category for continuously verifying the physical existence, location, and condition of fixed assets and reconciling that evidence against ERP financial records. Asset Relationship Management sits above ERP systems as an evidence layer. An ERP records what assets should exist based on transactions. An ARM system captures and maintains proof of what actually exists, using field inspections, RFID and GPS smart tags, AI document extraction, and orchestration workflows that push verified updates back into the ERP. Verification runs continuously, not once a year during a physical count. What separates ARM from mobile verification tools that also integrate with an ERP is orchestration: ARM schedules the work, routes it to the person closest to the asset, escalates exceptions, and governs approval before anything reaches the subledger. SoloTruth ARM is the first commercial platform built on that orchestration layer.

See also: Fixed asset orchestration · Evidence layer · Continuous verification · Governed workflow

Accounting Standards Codification 360 governs impairment testing for long-lived assets under U.S. GAAP. Formally ASC 360-10, Property, Plant, and Equipment. Step 1 compares the carrying value of an asset group to its undiscounted future cash flows. If carrying value exceeds those cash flows, a Step 2 fair value measurement is required, a full appraisal exercise that is expensive and audit-intensive. Ghost assets inflate carrying values, causing asset groups to fail Step 1 tests they would otherwise pass. The standard assumes the fixed asset register accurately reflects what assets exist and what they are worth. It cannot account for disposed assets still on the books or assets carrying overstated values because the register was never reconciled.

See also: Carrying value · Asset group · False impairment signal · The Impairment Test Your Register Is Failing

The lowest level of identifiable cash flows used in ASC 360 impairment testing. Impairment is assessed at the asset group level, not for individual assets. A single ghost asset inflating the carrying value of its group can trigger a Step 2 impairment test for the entire group. This is why register accuracy at the individual asset level has consequences that scale well beyond that one record.

See also: ASC 360 · Impairment testing

An asset filed under the wrong category in the fixed asset register, such as a vehicle recorded as machinery or furniture recorded as computer equipment. Each category usually carries a standard useful life, so a misfiled asset inherits the wrong life and is depreciated on the wrong schedule every year it stays on the books. Misclassification is a classification-accuracy problem, distinct from ghost and zombie assets, which are existence and completeness problems. It usually starts at purchase, when the category is picked from the invoice description rather than from the equipment.

See also: Useful life · Depreciation study · Depreciation schedule · A Depreciation Study Is Only as Good as the Record Under It

The process of comparing physical asset verification data, meaning existence, location, condition, and attributes, against fixed asset records in an ERP system and resolving the discrepancies. Asset reconciliation is the step that turns field evidence into trusted financial data. Discrepancies found during physical verification, including ghost assets, missing assets, location errors, and condition differences, are reviewed, approved, and pushed as corrections into the ERP fixed asset subledger. Historically this required manual review at every step. Modern platforms using AI and orchestration automate exception routing and ERP write-back, replacing manual reconciliation workflows.

See also: Subledger reconciliation · Governed workflow

The single date on which a jurisdiction fixes what a business owned for property tax purposes, regardless of what happened before or after it. Texas and California both set this date at January 1. The return reports the taxpayer's physical property position on that day, so an asset disposed of in February and an asset acquired in December are treated identically, because neither was there on January 1. That makes fixed asset register accuracy time-specific in a way financial reporting is not. A physical count taken in June supports an inference about January 1 rather than a record of it, which is why an annual count and continuous verification are not interchangeable for this purpose.

See also: Business personal property tax · Rendition · Physical verification · Ghost Assets Are Still on Your Property Tax Return

A governed workflow that captures physical evidence of asset existence, location, and condition, routes it through documented human review, and synchronizes verified results to the fixed asset register, producing a chain of custody auditors can evaluate. An audit-ready pipeline has five properties: a complete evidence chain from physical observation to ERP entry; defined human review points with documented decision authority and rationale records; a consistent, repeatable process that is not ad hoc; a materiality gate that controls which changes trigger an ERP write; and evidence that is independent of the underlying data source. Most fixed asset workflows fail at least one of these. The gap between having a system and having proof is what PCAOB AS 1105 now requires auditors to evaluate.

See also: PCAOB AS 1105 · HITL controls · Your Auditor Now Has to Trust Your Process, Not Just Your Numbers

A timestamped, traceable record of every action taken on an asset finding, from initial evidence capture through human review, approval or rejection, and final ERP update. An audit trail is the chronological record of what happened. It is distinct from the evidence itself and from the workflow that produced it. SoloTruth ARM maintains a continuous audit trail so every subledger change is backed by a defensible evidence chain rather than an unexplained adjustment.

See also: Fixed asset evidence · Governed workflow

See Carrying value.

An annual local tax on the tangible equipment a business owns, assessed on what the business physically holds on a fixed date rather than on what its accounting records show. The filing standard is physical, not accounting. California's 2026 business property statement instructs that equipment actually removed from the site is excluded from the return, while equipment retired in the books but still on the site must still be reported. Texas requires a rendition of income-producing tangible personal property owned, or managed and controlled as a fiduciary, on January 1. An accounting retirement therefore does not by itself change the taxable position, and a fixed asset register that has drifted from physical reality produces a wrong return in whichever direction it drifted. No jurisdiction examined requires a physical inspection before an asset comes off a return. What the rules require is documentation of the disposal.

See also: Assessment date · Rendition · Ghost asset · Ghost Assets Are Still on Your Property Tax Return

The net value of a fixed asset as recorded in the financial subledger: original acquisition cost minus accumulated depreciation. Also called book value. Carrying value is the figure used in impairment testing under ASC 360 and IAS 36. Ghost assets inflate it, creating false impairment risk and overstated balance sheet values. Carrying value is only as reliable as the register behind it. When the fixed asset register has never been reconciled against physical reality, carrying value is an assumption presented as a number.

See also: ASC 360 · Impairment testing · Phantom depreciation

A property insurance provision that requires the insured to carry coverage equal to a stated percentage of the property's value, and reduces claim payments when coverage falls short of it. A coinsurance clause turns an understated schedule of values into a smaller claim check. If the insured value is below the required percentage when a loss happens, the insurer pays only a proportion of the loss, even on property that was listed. When the equipment lines on a schedule start from the fixed asset register, unrecorded additions and stale values on the register can carry straight into a coinsurance shortfall.

See also: Schedule of values · Margin clause · Your Property Insurance Schedule Starts in the Fixed Asset Register

The audit assertion that everything that should be recorded in a company's records is in fact recorded, the test designed to catch understatement rather than overstatement. PCAOB Auditing Standard 1105, paragraph 11, defines completeness alongside existence as one of the assertions relevant to an audit. Testing completeness means starting from what physically exists, not from the register, because a procedure that starts from the register can only confirm what the register already contains. This is the harder, less commonly run direction of physical asset verification, sometimes called floor to book.

See also: Existence assertion · Floor to book · Fixed asset register

The requirement under IAS 16 to depreciate significant components of a fixed asset separately when those components have different useful lives. A manufacturing line's motor and its structural frame must be tracked as distinct assets. When a component is replaced without a corresponding subledger update, the replaced component becomes a ghost, and the new component is expensed rather than capitalized. Component accounting multiplies the number of records that have to stay accurate, which multiplies the exposure when no verification layer exists.

See also: IAS 16 · Useful life · Ghost asset

A financial reporting method that depreciates a group of similar assets at one blended rate rather than tracking each asset's depreciation individually. Composite and group depreciation is a bookkeeping convention, not a tax rule. When one asset in the group is retired without a recorded disposal, the accounting entry can net to zero on the balance sheet, since the group's blended rate absorbs the change. That accounting outcome does not carry over to tax treatment. Under MACRS, the IRS tracks an individual asset's disposition separately unless the company has made a formal general asset account election, so an unrecorded retirement can still leave an asset depreciating for tax purposes after it is gone, or forgo a deductible loss the company was entitled to take.

See also: General asset account (GAA) election · Depreciation schedule · Fixed asset register

The practice of recording an asset's physical condition, meaning its wear, damage, or fault severity, at the point of observation, so condition becomes actionable data rather than an unlogged judgment. Location and existence are objective and easy to log. Condition is subjective, which is why it rarely reaches a system of record without a governed path. Condition capture puts that judgment into a structured workflow. An operator flags what they see during normal work, the finding is triaged by severity, and it routes to the maintenance system as a work order or to the ERP as a value adjustment, reviewed and logged along the way. Capturing condition continuously, between scheduled maintenance windows, is where much of the operational value of asset verification sits, because problems surface as a planned fix instead of as downtime.

See also: Idle or non-functional asset · ARM: The Orchestration Layer Between Workforce, ERP, and Maintenance

A model in which fixed asset existence, location, and condition are verified on an ongoing basis, triggered by physical events, rather than during a scheduled annual count. Continuous verification eliminates the 11-month drift window created by annual physical audits. It uses IoT sensors, RFID and GPS tracking, AI extraction, and orchestration software to keep fixed asset records synchronized with physical reality in near real time, replacing the once-a-year inventory and the audit-prep scramble with a live control layer that operates between audits. The Omdia 2025 IoT Enterprise Survey found that 60 percent of manufacturers are already deploying stationary asset monitoring at scale. Continuous verification connects that sensor data to the fixed asset financial subledger.

See also: Data drift · Physical verification · Why Fixed Asset Verification Is Finally Practical · Continuous Verification Is the New Standard for Fixed Asset Accuracy · Asset Verification Is a Function, Not an Annual Project

The EU regulation requiring in-scope companies to report detailed sustainability data under the European Sustainability Reporting Standards (ESRS). Following the Omnibus I revision, CSRD applies from FY2027 to companies with 1,000 or more employees and more than 450 million euros in turnover. ESRS E1 requires companies to report assets at material physical climate risk at NUTS Level 3 geographic coordinates, meaning county or district level precision. That requirement cannot be satisfied from a static ERP fixed asset register, because the register records financial transactions rather than verified physical locations. ESRS E5 adds resource use and circular economy disclosures, which Omnibus I trimmed substantially in 2026.

See also: GPS · Physical verification

The gradual divergence between what an ERP fixed asset register records and what physically exists. Data drift accumulates continuously as assets are moved, retired, replaced, or added without corresponding journal entries. Annual physical counts reset drift temporarily. Continuous verification eliminates it. Drift is the mechanism. The fixed asset evidence gap is the structural condition that lets it accumulate unchecked.

See also: Fixed asset evidence gap · Manual journal dependency · Continuous verification

The asset value a policyholder reports to an insurer, which is what the policy is actually underwritten on. Insurers price and settle against the values the insured supplies, not against an independent valuation they perform themselves. A declared value based on original cost, or on an estimate nobody has revisited, produces underinsurance that surfaces at claim time rather than at renewal. The same condition and location evidence that supports a depreciation schedule is what keeps a declared value defensible.

See also: Carrying value · Condition capture · Physical verification · An Accurate Fixed Asset Register Is Not the Finish Line

The accounting record that allocates each fixed asset's cost across its useful life, producing the periodic depreciation expense on the income statement and the accumulated depreciation carried on the balance sheet. A depreciation schedule is built from assumptions set when an asset is capitalized: that the asset exists, sits where it was recorded, and holds the condition and useful life assigned to it. Those assumptions are rarely re-tested after acquisition, so the schedule runs a capitalization-day snapshot forward regardless of what changes on the floor. When assets are moved, cannibalized, or scrapped without a corresponding entry, the schedule keeps depreciating records that no longer match reality. Depreciation schedule accuracy therefore depends on whether existence, location, and condition are verified on an ongoing basis, not on the precision of the calculation itself.

See also: Useful life · Phantom depreciation · Your Depreciation Schedule Is Built on Assumptions

A periodic review, often done by an outside specialist, that tests whether the useful lives in the fixed asset register still match how long the equipment lasts. A study estimates lives mainly from the company's own history of what was bought and what was retired, so it reads the register rather than walking the floor asset by asset. It follows, as reasoning rather than a rule, that a study can only be as accurate as that record: a retirement never booked reads as an asset that survived, and a misfiled asset is reviewed under the wrong category.

See also: Useful life · Asset misclassification · Retired asset · A Depreciation Study Is Only as Good as the Record Under It

The removal of a fixed asset from the financial statements. Under IAS 16 and ASC 360, an asset must be derecognized when it is disposed of, retired, or when no future economic benefits are expected from its use. Failure to derecognize creates ghost assets, records that continue to depreciate on the books after the asset no longer exists. Derecognition depends on someone observing the disposal and someone else filing the entry, which are rarely the same person.

See also: Ghost asset · Manual journal dependency

Software covering maintenance work orders, asset health, and operational uptime. Examples include IBM Maximo and SAP Plant Maintenance. EAM optimizes operational performance. It does not reconcile physical asset existence against the financial subledger. SoloTruth ARM sits above EAM and governs what happens between a physical finding and the financial record update.

See also: ARM · Module silo

Enterprise software platforms, including SAP, Oracle, Microsoft Dynamics, and TOTVS, that manage financial records, supply chain, and operations. ERP fixed asset modules record the financial lifecycle of assets accurately. They were never designed to verify that the assets physically exist. An ERP records what it is told. It cannot detect physical changes that go unreported.

See also: ERP design constraint · Fixed asset register

The structural limitation of ERP systems with respect to fixed asset accuracy: they are transaction-based systems designed to record financial events, not to verify physical reality. An ERP records an asset acquisition when an invoice is processed. It records a disposal when someone enters a disposal transaction. It does not independently confirm whether assets exist, have moved, or have been informally retired. This is not a flaw. It is how ERP systems are designed. The constraint means fixed asset register accuracy depends entirely on whether every physical event in an asset's lifecycle is captured as a corresponding ERP transaction. In practice, many are not. The constraint expresses itself through two specific mechanisms: manual journal dependency and module silo.

See also: Manual journal dependency · Module silo · The Impairment Test Your Register Is Failing · Physical inventory (ERP) · Asset Verification Is a Function, Not an Annual Project

SoloTruth's term for the capability that sits between physical asset reality and the financial system of record. The evidence layer captures multi-source physical data from inspections, RFID, GPS, and documents, routes it through governed workflows, and writes verified results to the ERP. It replaces the assumption that journal entries will be filed manually. The evidence layer is the capability. Fixed asset evidence is what it produces.

See also: Fixed asset evidence · ARM

The audit assertion that assets recorded in a company's books actually exist, the test designed to catch overstatement rather than understatement. PCAOB Auditing Standard 1105, paragraph 11, defines existence alongside completeness as one of the assertions relevant to an audit. An annual physical count typically tests existence: it starts from the register and walks the floor to confirm each listed item is still there. It does not test completeness, because it never looks past what the register already lists. Sometimes called book to floor.

See also: Completeness assertion · Floor to book · Ghost asset

An impairment trigger or impairment loss that results from inaccurate fixed asset register data rather than genuine economic deterioration of the underlying assets. A false impairment signal occurs when ghost assets or disposed assets inflate the carrying value of an asset group above its recoverable amount. The assets themselves may be performing normally. The impairment charge reflects a data accuracy problem, not a business problem. False impairment signals can trigger unnecessary write-downs, distort financial statements, and create audit deficiencies. They are distinct from genuine impairments, which reflect real economic deterioration, because the underlying assets retain their value.

See also: ASC 360 · Partial ghost asset · The Impairment Test Your Register Is Failing

The SAP module that manages the fixed asset subledger. FI-AA handles acquisition cost, depreciation, and retirement. It is a separate module from SAP Plant Maintenance and does not receive automatic updates when physical changes occur on the floor. This module silo is a design constraint, not a configuration problem, and no amount of SAP configuration closes it.

See also: Module silo · S/4HANA migration

Verifiable, documented proof of a fixed asset's identity, location, and condition, attached to the financial record and available for audit, insurance, and compliance purposes. Fixed asset evidence is the output of a physical verification process. It is not an ERP field or a recorded transaction. It is documentation: inspection photos, RFID scan records, GPS coordinates, work orders, and supporting documents that prove the asset described in the register matches what physically exists. Evidence is what auditors, insurers, and acquirers require when they need more than a system record.

See also: Evidence layer · Audit trail

The structural discrepancy between what an ERP system records about a company's fixed assets and the physical reality of those assets. ERP systems track financial transactions: acquisition cost, depreciation, recorded disposals. They cannot independently verify whether a physical asset still exists, is in the correct location, or is in the condition the record assumes. Every undocumented disposal, informal asset move, or cannibalized piece of equipment widens this gap. Most companies discover it once a year during a physical inventory. The rest of the year, they operate on a register that is, at best, approximate. SoloTruth coined this term to describe a structural design problem, not a bookkeeping failure.

See also: Data drift · ERP design constraint · The Fixed Asset Evidence Problem

The coordination layer that schedules inspections, delegates tasks to the right people, escalates exceptions, routes approvals, and writes confirmed data back to the ERP, continuously and at scale, without manual coordination at every step. Capture tools such as RFID readers, IoT sensors, and inspection apps collect evidence about an asset's location, condition, and existence. Orchestration is what happens after capture. It routes, validates, escalates, approves, and records that evidence so it becomes accurate, governed financial data. Without orchestration, captured data accumulates in silos and never reaches the fixed asset subledger through a defined process. Fixed asset orchestration has four functions that must work together: schedule, delegate, escalate, and approve. Remove any one and the chain breaks.

See also: Universal Orchestration · Governed workflow · You Solved the Capture Problem. You Haven't Solved Orchestration.

The official list of a company's fixed assets maintained in the ERP or fixed asset subledger, tracking acquisition cost, accumulated depreciation, net book value, useful life, location, and assigned cost center for each asset. The FAR feeds the general ledger, and its accuracy depends entirely on the journal entries it receives. It is the financial record of what a company believes it owns, not a physical inventory. Because ERP systems record assets based on transactions rather than physical observation, the register reflects what should exist, not what does. Inaccuracies accumulate silently through undocumented disposals, asset moves, and physical deterioration. Without a verification layer, the register reflects what organizations believe they own, not what they can prove they own. The register is also the input to impairment testing under ASC 360. If the register is wrong, the impairment test cannot produce a reliable result.

See also: Subledger · Data drift · ASC 360 · The Impairment Test Your Register Is Failing

Verification that starts with the physical assets a company actually has and checks whether each one is properly reflected in the fixed asset register, the reverse of the more common book to floor direction. Floor to book is how the completeness assertion gets tested in practice. Most annual physical counts only run book to floor, starting from the register and confirming each listed item still exists. That direction cannot find an asset that was added, swapped in, or moved on-site but never entered into the register, because it never looks past the list. Floor to book closes that gap by starting from what is physically present instead.

See also: Completeness assertion · Existence assertion · Continuous verification · Zombie asset · Your Fixed Asset Register Only Gets Checked One Way

An asset whose accumulated depreciation equals its cost, so its net book value on the fixed asset register is zero even though it may still be in service. A fully depreciated asset stays on the register until it is retired. Because it carries no book value, no one sees a financial reason to record its retirement when it leaves service, which makes it one of the six ways ghost assets get onto a register. It can still inflate asset counts, insured values and, in some jurisdictions, property tax listings.

See also: Ghost asset · Useful life · Six Ways Ghost Assets Get Onto a Fixed Asset Register

A formal election under U.S. tax law that lets a company treat a defined group of assets as a single account for depreciation purposes, so that an individual asset's disposition generally does not affect the account's basis or depreciation reserve. A GAA election is a tax-specific choice, distinct from composite or group depreciation used for financial reporting. The two can look similar in effect, both absorb an individual retirement into a group-level number, but having one does not mean a company has the other. Without a valid GAA election, an unrecorded retirement is its own event under IRS rules (Publication 946, Publication 544), independent of whatever depreciation convention governs the books.

See also: Composite depreciation · Depreciation schedule

A fixed asset that remains on the ERP register and continues to depreciate, generate insurance premiums, and appear in audit samples, but no longer physically exists. Ghost assets accumulate when assets are retired, cannibalized, lost, or stolen without a corresponding disposal entry. Kroll Advisory's fixed asset register health check found more than 15 percent of recorded assets no longer in service at one manufacturing client. Treat any industry-wide percentage with caution, including the 10 to 30 percent range that circulates widely: no published prevalence study for ghost assets discloses a sample size or a method. The financial exposure includes phantom depreciation, property tax overpayments, insurance premiums on assets that do not exist, and false impairment test triggers. Ghost assets also create audit deficiencies under PCAOB long-lived asset testing standards. SoloTruth ARM eliminates ghost assets by continuously reconciling physical verification evidence against the fixed asset register.

See also: Zombie asset · Partial ghost asset · Phantom depreciation · What the Fixed Asset Evidence Gap Actually Costs

One look at an asset that gathers and verifies photographic, condition and other asset evidence, with location and a timestamp, and is reviewed by accounting before the fixed asset register changes. The review is what makes the visit governed rather than just a photo. Because depreciation, the insurance schedule of values, the tax treatment of retirements and the fixed-asset audit all draw on the same register, one visit captured and approved this way keeps all four current at once, instead of four teams collecting the same facts separately.

See also: Governed workflow · Schedule of values · Existence assertion · One Field Visit Feeds Four Fixed Asset Records

A structured process that routes a finding or exception to the correct reviewer, requires a human decision at defined points, and logs every action before a system-of-record update executes. SoloTruth ARM uses governed workflows so no asset register change happens without evidence, accountability, and a traceable approval chain. A governed workflow is the mechanism. HITL controls are the specific checkpoints inside it.

See also: HITL controls · Fixed asset orchestration · Audit trail

Location tracking technology used to capture outdoor and large-facility asset positions. In fixed asset verification, GPS confirms that assets are located where the register claims and supplies the physical location evidence that climate risk disclosure requires. Unlike RFID, GPS reports position without needing the asset to pass a reader, which suits vehicles, yard equipment, and assets spread across large sites.

See also: RFID · CSRD · Physical verification

Governance checkpoints designed into an automated workflow at which a named human reviews evidence, makes a decision, and records their rationale before the process continues. In fixed asset management, HITL controls are what turn captured field data into defensible audit evidence. A HITL control is not a signature page or a periodic approval meeting. It has four required properties: the reviewer has full context of what they are evaluating; they have defined decision authority over what they are approving; their decision and rationale are logged with a time stamp; and the process is time-boxed so exceptions are escalated rather than abandoned. Under PCAOB AS 1105, evidence produced by a workflow with well-designed HITL controls is structured to satisfy the reliability requirements auditors must evaluate. Evidence produced without them is not. SoloTruth ARM applies human-in-the-loop control to every financially material asset finding. Automation routes and proposes. Humans decide and approve.

See also: Governed workflow · PCAOB AS 1105 · Your Auditor Now Has to Trust Your Process, Not Just Your Numbers

The IFRS standard governing property, plant, and equipment. IAS 16 requires component accounting, meaning significant components with different useful lives must be depreciated separately. It also governs initial recognition, revaluation, and derecognition of fixed assets. Most organizations using SAP FI-AA carry a structural gap between what IAS 16 requires and what the ERP actually captures.

See also: Component accounting · Derecognition · FI-AA

The IFRS standard governing impairment of assets, including when an entity must test whether an asset is still worth what the books say. IAS 36 names evidence of physical damage or obsolescence as an indicator that an asset may be impaired, which makes a physical observation an accounting trigger rather than a maintenance note. Where the entity now expects to abandon the asset earlier than planned, the standard also requires the depreciable period to shorten. It sets no numeric damage threshold. The test is evidence-triggered, which means it depends entirely on somebody observing and recording the condition.

See also: Impairment indicator · Impairment testing · IAS 16 · ASC 360 · An Accurate Fixed Asset Register Is Not the Finish Line

AI-powered extraction, classification, and interpretation of unstructured documents, including invoices, bills of materials, maintenance records, and purchase orders. In fixed asset management, IDP extracts asset attributes from source documents and feeds them into the reconciliation workflow, removing manual data entry. Extraction alone does not produce a governed record. The extracted attributes still require review and approval before they reach the subledger.

See also: Governed workflow · Fixed asset evidence

A fixed asset that is correctly recorded and correctly located in the fixed asset register, but is broken, unused, or no longer contributing operational value. Unlike ghost assets and zombie assets, idle or non-functional assets have no established, industry-standard category name. SoloTruth uses this descriptive term because accounting and asset-management standards typically address this state through operating versus non-operating classification or an ASC 360 impairment test, not a named category. An RFID tag reads identically whether the asset behind it works or has sat broken for a year, so detecting an idle or non-functional asset requires a field operator's direct condition check, not a location or existence signal. Left unflagged, it can sit at full carrying value on the books as an unrecognized impairment candidate.

See also: Condition capture · Ghost asset · Zombie asset · The Fixed Asset Gap RFID Alone Can't Close

A fact or observation that obliges an entity to test whether an asset's carrying value is still supportable. Under IAS 36, physical damage and obsolescence are named indicators. Under U.S. GAAP, ASC 360-10-35-21 names a significant adverse change in an asset's physical condition as a triggering event for a recoverability test. Neither framework sets a percentage of degradation that fires the test automatically, so the indicator only exists in practice once the physical condition has been observed and documented. An unobserved indicator is still an indicator, and the obligation does not wait for the annual count.

See also: IAS 36 · ASC 360 · Impairment testing · Condition capture · An Accurate Fixed Asset Register Is Not the Finish Line

The process of determining whether a long-lived asset's carrying value exceeds its recoverable amount under IFRS and IAS 36, or its undiscounted future cash flows under U.S. GAAP and ASC 360. Ghost assets inflate carrying values and can trigger impairment tests, including full Step 2 fair value measurements, on asset groups that would otherwise pass. The test is only as good as the register that feeds it. An impairment test run against an unverified register measures the accuracy of the bookkeeping as much as the economics of the assets.

See also: ASC 360 · Asset group · False impairment signal

The value a property insurer uses for coverage, normally the cost to replace or reproduce an asset rather than its book value. Insurable value and book value measure different things. Book value is cost minus accumulated depreciation, so it falls to zero over an asset's useful life. Insurable value reflects what it would cost to replace the asset today, so a fully depreciated machine can still carry a large insured value. That gap is why a ghost asset with no remaining book value can still add premium when it stays on a schedule of values.

See also: Schedule of values · Fully depreciated asset · Your Property Insurance Schedule Starts in the Fixed Asset Register

A register error where a serialized, reusable asset leaves a site and a physically identical unit returns in its place, so quantities reconcile while the register is wrong at serial level. A like-kind swap is the one ghost asset mechanism a physical count cannot catch, because counts reconcile totals rather than identities. The acquisition date, cost, accumulated depreciation and remaining useful life on the record all attach to the wrong unit. It is most common in pooled or cycled assets such as returnable containers, tooling, test equipment and IT hardware, and it is the clearest argument for serial-level identity over quantity accounting.

See also: Ghost asset · Floor to book · Six Ways Ghost Assets Get Onto a Fixed Asset Register

A written statement from a company's management to its auditor confirming facts about the financial statements, such as that the recorded assets exist. Audit standards say plainly that a management representation is not sufficient evidence on its own, and that obtaining one does not reduce the other procedures the auditor has to perform. For fixed assets, the representation says the equipment exists; something else has to show it. A purchase invoice or a work order shows that a transaction happened, not that the asset is still there today.

See also: Existence assertion · Completeness assertion · Two Audit Tests, Two Kinds of Fixed Asset Register Error

The structural requirement in every major ERP that physical asset changes, including retirements, relocations, and component replacements, must reach the register through manually filed journal entries. The people who observe physical changes, meaning maintenance crews and plant floor staff, are rarely the people who file accounting entries. This gap is where register drift originates. It is not a training problem. It is a structural mismatch between who sees the change and who records it.

See also: ERP design constraint · Data drift · Derecognition

A property insurance provision that caps what the insurer pays at any one location relative to the value reported for that location on the schedule of values. A margin clause makes per-location accuracy matter, not just the total. When equipment moves between sites without a record, one location's reported value runs high and another's runs low, and a loss at the understated site is capped at a value that is too low. Insurers have mandated margin clauses where schedules were inaccurate or under-reported, as Aon's Q3 2023 market overview describes.

See also: Schedule of values · Coinsurance clause · Your Property Insurance Schedule Starts in the Fixed Asset Register

The design constraint in SAP, Oracle, and Microsoft Dynamics where the physical tracking module and the fixed asset financial subledger are not natively integrated. Physical changes captured in Plant Maintenance or Inventory Management do not automatically update the fixed asset subledger. This is not a configuration problem. It is a design constraint that applies to every major ERP platform, which is why the fix has to sit above the ERP rather than inside it.

See also: ERP design constraint · FI-AA · EAM

The distance between what a fixed asset register says about an asset and what the person operating it already knows, a gap that opens the moment the register was last updated and widens every day after. The register updates on defined events: a purchase, a disposal, a scheduled count. A person operating an asset notices changes continuously, wear, minor damage, drift, but has no defined path to route that observation into the record. The gap is structural, not a diligence failure on either side.

See also: Completeness assertion · Continuous verification · Fixed asset register (FAR) · Your Forklift Operator Already Knows What Your Register Doesn't

Equipment a crew has taken out of use while it remains owned and remains on the fixed asset register. An out-of-service asset may return after a repair, or it may later be retired or disposed of. The status change happens on the floor, while the record change has to happen in accounting, and if nobody owns the step between them the register keeps reporting the asset as in service. Out of service is a status, not an outcome: it needs a review date and a named owner who decides what happens next.

See also: Retired asset · Idle or non-functional asset · Ghost asset · Out of Service Is Not Retired: Who Owns the Change to the Asset Record

A fixed asset that physically exists but has been partially cannibalized, stripped, or degraded, while its full original value remains on the fixed asset register. Partial ghost assets are more common than fully disposed ghost assets in industrial environments. A piece of equipment may have had components removed for use elsewhere, suffered damage reducing its remaining useful life, or been decommissioned in place without a formal disposal. The ERP record reflects the original acquisition value and depreciation schedule, not the asset's actual current state. Partial ghost assets overstate the carrying value of the asset group, increasing the risk of a false impairment signal under ASC 360.

See also: Ghost asset · Component accounting · False impairment signal · The Impairment Test Your Register Is Failing

An RFID tag with no internal battery that registers a read only when it passes a powered reader or a fixed gate, producing existence and location confirmation at whatever interval a business schedules. Because the reader powers the read rather than the tag broadcasting on its own, passive RFID is the lower-cost tier, typically a few cents to a quarter per tag in volume. Deployed at doorways or dock exits, it delivers a periodic confirmation, weekly, monthly, or quarterly, of whether an asset is still where the register says it is. For most fixed asset registers, that periodic cadence is sufficient. Continuous tracking is rarely required just to keep the books accurate.

See also: Active RFID (RTLS) · RFID · The Fixed Asset Gap RFID Alone Can't Close

The U.S. regulator that oversees audits of public companies. PCAOB publishes annual inspection findings, including audit deficiency rates and the areas where inspectors most often find failures. In the PCAOB's 2024 inspection cycle, long-lived assets were the number one internal control over financial reporting deficiency area, even as overall audit deficiency rates improved. Organizations that cannot demonstrate physical verification of their asset register face increasing audit risk.

See also: PCAOB AS 1105 · SOX

The PCAOB standard governing audit evidence, amended effective for fiscal years beginning on or after December 15, 2025. The amended standard sharpens auditors' responsibility to evaluate the reliability of electronic information used as audit evidence, including data produced through technology-assisted analysis. Auditors must assess not just what a fixed asset register says, but how that information was produced. A fixed asset process that lacks documented governance, defined review authority, or a complete chain of custody from physical evidence to ERP entry makes it harder for auditors to establish that the supporting evidence is reliable. AS 1105 governs the auditor's responsibilities, not company requirements directly. The practical effect is still direct: an ungoverned, undocumented fixed asset pipeline creates audit exposure under heightened AS 1105 expectations.

See also: Audit-ready fixed asset pipeline · HITL controls · Your Auditor Now Has to Trust Your Process, Not Just Your Numbers

Depreciation charges posted to the income statement for assets that no longer physically exist. Phantom depreciation is the most direct financial cost of ghost assets. It overstates expenses, understates net income, and inflates carrying values on the balance sheet. It continues every period until someone derecognizes the asset, which is why ghost assets are a compounding cost rather than a one-time error.

See also: Ghost asset · Depreciation schedule · Derecognition

The count-and-reconcile function built into ERP fixed asset modules, which compares physical data the company supplies against the asset register and posts the differences. SAP, Oracle and Microsoft all document one. Oracle Assets includes a Physical Inventory feature, and Oracle states that to use it you must first take physical inventory of your assets, describing that as manually looking at all assets to confirm they exist as recorded, sit in the appropriate locations, and consist of the recorded number of units. SAP documents a physical inventory that the director of the organization orders, carried out by a commission that posts any differences into Asset Accounting. The distinction that matters is the direction of supply. The ERP reconciles evidence you give it. It does not go and gather that evidence, and gathering it is the job most companies run once a year.

See also: Physical verification · Continuous verification · ERP design constraint · Asset Verification Is a Function, Not an Annual Project

The process of confirming that a fixed asset physically exists at the location the register claims, in the condition the carrying value assumes, with the components the depreciation schedule depends on. Physical verification is distinct from ERP record-keeping. The ERP records what it was told. Physical verification confirms whether that information is accurate. Traditional physical verification is periodic, sampling-based, and backward-looking, typically conducted annually during audit preparation, so it tells you what was probably true at a point in time. Continuous verification uses IoT sensors, AI extraction, and orchestration software to keep the asset register synchronized with physical reality on an ongoing basis.

See also: Continuous verification · Fixed asset evidence · Why Fixed Asset Verification Is Finally Practical · Physical inventory (ERP) · Asset Verification Is a Function, Not an Annual Project

The US GAAP test under ASC 360 of whether a long-lived asset's carrying amount can be recovered from the cash flows it is expected to generate. A recoverability test is run when a triggering event suggests the carrying amount may not be recoverable. Under ASC 360-10-35-21, a significant adverse change in an asset's physical condition is itself a recognized triggering event. The standard sets no numeric threshold, so the trigger depends on someone observing the condition and getting that observation into the record.

See also: Impairment testing · Impairment indicator · ASC 360 · Out of Service Is Not Retired: Who Owns the Change to the Asset Record

A sworn statement filed with a Texas appraisal district listing the taxable business personal property a taxpayer owned or controlled on January 1. Texas requires rendition of income-producing tangible personal property owned, or managed and controlled as a fiduciary, on the assessment date. Because the statement is sworn, the accuracy of the fixed asset register behind it carries more weight than it does in an internal management report. A rendition prepared straight from a register nobody has physically verified reports whatever that register happens to say, which includes assets that left the site and excludes assets retired in the books but still standing on the floor.

See also: Business personal property tax · Assessment date · Fixed asset register (FAR) · Ghost Assets Are Still on Your Property Tax Return

The amount an entity expects to recover from an asset at the end of its useful life, after deducting expected disposal costs. Residual value sits directly in the depreciation calculation: the depreciable amount is cost less residual value, spread over the useful life. IAS 16.51 requires residual values, useful lives, and depreciation methods to be reviewed at each financial year end and adjusted going forward when the evidence has changed. A residual value estimated at acquisition and never revisited quietly distorts every period's depreciation charge until somebody checks the asset's actual condition.

See also: Useful life · Depreciation schedule · IAS 16 · Carrying value · An Accurate Fixed Asset Register Is Not the Finish Line

A fixed asset permanently removed from service, which the record should stop treating as productive. Retirement is a decision, not a location. A retired asset may still be standing on site awaiting sale or scrap, which is why it differs from a disposed asset that has left the company entirely. If the retirement never reaches the register, the asset keeps its carrying value and keeps depreciating, and an unrecorded retirement also has tax consequences of its own that are separate from the book side.

See also: Out-of-service asset · Ghost asset · Carrying value · Out of Service Is Not Retired: Who Owns the Change to the Asset Record

A radio identification method that confirms a fixed asset's existence and last known location by reading a small electronic tag attached to it, without line-of-sight scanning. An RFID reader detects a tag when it passes a fixed reader, a gate, or a mobile scanner, producing a signal for existence and last-verified location, and it can inventory large numbers of assets quickly. That signal closes one of the three common ways a fixed asset register goes wrong: the ghost asset, equipment recorded in the books that no longer physically exists. RFID structurally cannot detect an asset that was never tagged, which is the zombie asset. It cannot assess whether a tagged asset is actually functioning, which is the idle or non-functional asset. Both gaps require a person, not better hardware.

See also: Passive RFID · Active RFID (RTLS) · Zombie asset · Idle or non-functional asset · The Fixed Asset Gap RFID Alone Can't Close

The transition from SAP ECC, the legacy ERP platform, to SAP S/4HANA, the current generation. SAP ECC mainstream maintenance ends December 31, 2027, and roughly 17,000 ECC holdouts remain to migrate by then. Ghost assets in the legacy register migrate into the new system, compounding data quality problems at significant cost. Pre-migration physical verification is the most cost-effective point to clean the register, because the alternative is paying to carry known-bad data into a platform that will hold it for the next decade.

See also: FI-AA · Ghost asset · Physical verification

A commercial property insurance document listing the insured's covered property and the value assigned to each item, used by the insurer to set premium. A schedule of values is only as accurate as the last time someone updated it against physical reality. When equipment is retired, replaced, or written down internally but the schedule is never revised downward, the insured keeps paying premium against value that no longer exists. Major brokers, including Marsh, run valuation practices specifically to reconcile and cleanse a client's schedule of values and identify ghost assets within it, because the insured is the party who submitted the number that set the premium in the first place.

See also: Ghost asset · Fixed asset register

U.S. federal legislation requiring public companies to maintain effective internal controls over financial reporting. Fixed asset subledger accuracy is a SOX control. Ghost assets and unreconciled registers create control deficiency findings that require remediation and can escalate to material weaknesses. The exposure is not the accounting error itself. It is the inability to demonstrate that a control existed to catch it.

See also: PCAOB · Audit-ready fixed asset pipeline

The detailed subsidiary ledger within an ERP that tracks individual asset records and feeds aggregate balances to the general ledger. The fixed asset subledger is the source of depreciation charges, impairment test inputs, and audit schedules. Its accuracy depends entirely on the transactions it receives. The subledger is the record. Subledger reconciliation is the process that keeps it true.

See also: Fixed asset register · Subledger reconciliation

The process of writing verified physical asset data back to the ERP fixed asset subledger so the financial record reflects what physically exists. Subledger reconciliation is the final step in a continuous verification workflow. Evidence captured in the field, reviewed by a named approver, and approved for financial impact is pushed as a governed update to the subledger, retiring ghost assets, correcting locations, updating condition data, and closing the loop between physical reality and the financial record. Without it, verification produces accurate field data that never reaches the system of record. Direct, governed write-back is what distinguishes a continuous verification platform from an asset tracking tool.

See also: Subledger · Asset reconciliation · Continuous Verification Is the New Standard for Fixed Asset Accuracy

A software category, named by Gartner in February 2026, for the governance layer that coordinates AI agents, bots, APIs, and human workflows into a single governed process across an enterprise's systems. Universal Orchestration sits above individual AI agents and automation tools, deciding what each agent's output means, who reviews it, and how it reaches a system of record. Gartner rates the category HIGH innovation benefit and projects 90 percent enterprise adoption by 2029 (G00841113, February 2026). SoloTruth ARM is built on Axon Ivy's Universal Orchestration engine, applying the same governance model to physical fixed asset verification: routing asset findings through human-in-the-loop workflows and writing verified data to ERP systems.

See also: Agent sprawl · Fixed asset orchestration · Automation Plays an Instrument. Orchestration Conducts the Orchestra.

The estimated period over which a fixed asset is expected to generate economic benefits, and the basis for its depreciation schedule. Incorrect useful lives, whether too short or too long, are a common cause of register inaccuracy. Component replacements that go unrecorded create useful-life errors that compound over time, because the schedule keeps depreciating an original component that was replaced years earlier.

See also: Depreciation schedule · Component accounting

SoloTruth VirtuSpect is SoloTruth's inspection management platform for regulated lenders and compliance teams. SoloTruth VirtuSpect captures geo-tagged, timestamped, image-authenticated field evidence and routes it through governed review workflows, producing a complete audit trail from assignment through resolution. It has been in production at SBA and commercial lenders since 2024.

See also: Fixed asset evidence · Audit trail

An asset that is physically present and in use but has never been added to the fixed asset register. The inverse of a ghost asset. Zombie assets are not depreciated, not insured at correct values, not included in maintenance programs, and invisible to auditors. They enter during capital projects, transfer in from other locations, or get acquired informally through field and plant-floor purchases made below the formal capital review threshold, without anyone creating the corresponding financial record. Organizations usually discover them during physical counts or ERP migrations. No credible prevalence estimate exists for zombie assets, and on inspection none exists for ghost assets either: the 10 to 30 percent range that circulates widely traces back to a single consultancy's unpublished experience, with no disclosed sample and no stated method. Both categories are inconsistently defined across sources and only become visible through routine physical reconciliation, which most organizations do not run.

See also: Ghost asset · Idle or non-functional asset · RFID · Zombie Assets: Why No One Has a Reliable Number