Fixed asset terms, defined.

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

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

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.

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

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

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 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

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

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

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. Industry data from Kroll Advisory shows that 10 to 30 percent of fixed assets at typical enterprises are ghosts. 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

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

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

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 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

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

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

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

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, unlike the 10 to 30 percent range Kroll Advisory publishes for ghost assets, because the category is inconsistently defined across sources and only becomes 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