The Many Meanings of “Asset” in Technology Costing
In technology costing it’s important to have leaders and teams from various domains and functions come together to collaborate on the building and telling of an organization’s cost story. Commonly, our peers and partners will discover that the same language appears in different domains and means different things to different people, and that initial confusion can create friction.
A great example of this occurrence is when Finance, IT Asset Management, and ServiceNow teams all use the word “asset,” and each group means something different when they say it. The resulting conversations and challenges are predictable; someone asks a question about depreciation, someone else answers with an ITAM definition, and a third person references a CI relationship in ServiceNow. Everyone is using the same word, but the conversation is not actually about the same thing.
It’s not a sign that anyone is wrong, it just means that the same word carries different meaning depending on the domain or function using it.
Finance: Assets That Depreciate
Finance uses the word “asset” in a standards-aligned, regulated way. Under the rules of GAAP and IFRS, fixed assets are long-lived items having a historical cost that is expensed as depreciation over an item’s useful life. In this context, a server, network switch, storage array, or software implementation is a fixed asset. Its initial cost is capitalized and sits on the organization’s balance sheet, and that cost is then expensed as depreciation over a period of time.
In example: A server rack purchased for $120,000 doesn’t become a $120,000 expense when the invoice is paid. Instead, it becomes a $120,000 asset on the organization’s balance sheet and a $2,000 monthly depreciation expense over the five-year period Finance has determined, with GAAP or IFRS guidance, that it will provide economic benefit.
IT Asset Management: Assets That Need Lifecycle Stewardship
IT Asset Management uses the word “asset” to mean something operational. In ITAM, an asset is a technology item that needs lifecycle management including procurement, assignment, maintenance, and retirement. In this context, laptops, servers, mobile devices, and sometimes software licenses are assets.
Some ITAM assets are also fixed assets that are depreciating, but some are likely not as well. ITAM may store financial attributes like purchase price or renewal dates, but it doesn’t determine or rely on whether an item is capitalized or how it depreciates. Instead, ITAM’s purpose is to ensure the organization knows what it owns, where it is, who uses it, and when it needs to be replaced.
ServiceNow: Assets and CIs That Describe the Operational Environment
In ServiceNow an “asset” is a financial or physical item tracked for ownership and lifecycle, and a configuration item (CI) is an operational component tracked for relationships, dependencies, and service health.
ServiceNow’s Asset Management focuses on ownership, cost, and lifecycle while CMDB focuses on operational relationships, service mapping, and dependency tracking. These two structures intersect, but they are not the same dataset and don’t serve the same purpose. In this context, some assets are CIs, some CIs are assets, and some are neither.
ServiceNow’s definitions are designed for operational clarity. They help teams understand how components relate to each other, how services are delivered, and how changes flow through the environment.
Bringing the Definitions Together
Looking at the three meanings or usages of the word “asset” side by side, the commonality is in that an asset is something an organization owns. The overlap between these definitions is why cross‑functional conversations often drift unless someone anchors the discussion in the correct meaning of the word for the conversation at hand.
Finance (fixed/capitalized) assets depreciate.
ITAM assets need lifecycle management.
ServiceNow assets and CIs describe operational relationships.
And to keep things fun and interesting, keep in mind that:
Some assets are fixed assets.
Some assets are operational assets.
Some assets are configuration items.
Some assets are all three.
Some assets are none.
The definitions overlap, but each exists for a different purpose and reflects a different view of the technology environment.
The Practitioner’s Role
Practitioners sit at the intersection of these definitions and act as translators. The goal is to help Finance understand how technology actually works without needing to turn Finance teams into operational experts. Likewise, technologists don’t need to become accountants to understand how financial processes shape their cost picture.
Most importantly, practitioners help everyone uses the word “asset” in a way that fits the conversation they’re having. No one needs deep expertise in all three domains to move forward, but they do need clarity about which definition is in play and how it relates to the others. These cross-domain translations make conversations smoother, decisions easier, and the financial picture more meaningful for everyone involved.
